Bug#827627: Please support packaging vim addons as vim "packages"

[James McCoy]

On Sat, Jun 18, 2016 at 09:41:12PM -0700, Josh Triplett wrote:
> On Sat, Jun 18, 2016 at 11:55:17PM -0400, James McCoy wrote:
> > On Jun 18, 2016 6:03 PM, "Josh Triplett" <josh at joshtriplett.org> wrote:
> > > I would suggest installing packages under /usr/share/vim/packages, and
> > > replacing the "files" key in the registry yaml files with "package:
> > > pkgname", where pkgname matches the top-level directory in
> > > /usr/share/vim/packages.  When installing a package, vim-addon-manager
> > > should just make a single symlink from ~/.vim/pack/$pkgname to
> > > /usr/share/vim/packages/$pkgname.
> > 
> > Good suggestions.  We currently use ~/.vim/bundle iirc, but since I don't
> > think it's really used anywhere, I'd be fine changing it.
> 
> Some of the "automatically download and run code from github" plugin
> systems use "bundle".  vim's built-in package handling uses "pack".

Thinking about this more, I'm considering a slight adaptation.  Rework
the expected policy for the "directory" type addon (which was never
officially released) to install under
/usr/share/vim/packages/pack/dist-bundle/start and have a new "package"
type addon which installs under /usr/share/vim/packages/pack (and should
include start/ and/or opt/ as needed).  /usr/share/vim/packages would be
added to 'packpath' by debian.vim (or similar).

Basically, all the existing addons could easily be changed to
"directory" addons and if someone starts providing actual Vim packages,
those are already supported.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB