Hello,

What's the best place to put bundled Vim plugins now that vim82 has a
new package system? From the documentation, /usr/share/vim/vim82/pack/
is the global directory for such plugins (and I have confirmed it works correctly) however, Lintian complains about the location.

Should I still place them according to how vim-plugin-manager expects?

--
Thanks,
Jai

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2021-09-05 15:19:33 +1000, Jai Flack wrote:

Hello,

What's the best place to put bundled Vim plugins now that vim82 has a
new package system? From the documentation, /usr/share/vim/vim82/pack/
is the global directory for such plugins (and I have confirmed it works correctly) however, Lintian complains about the location.

Should I still place them according to how vim-plugin-manager expects?

Based on what the (neo)vim maintainer has done with vim-scripts, vim-plugin-manager is being phased out. I haven't seen any efforts to coordinate a transition to vim's packaging system, but I suppose looking
at vim-scripts is a good starting point on how to install plugins for
both vim and neovim.

Cheers
--
Sebastian Ramacher

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmFcBSsACgkQafL8UW6n GZNgpg/+OjBycTaDCgBVoJwHWxhU4+d20w5cBtadZ8vPUNzBzSwRkob31h5Nulzd RuTORhXN60cppOIUvh51CgJLF67dpYeKLB2Lp/ZiHk3aOEOR4yDi0WrIJOj012ou oenfWHoZ9f1EgAdcnlYBg6eWRl1s4EPYsOZLtOjuct73A1p8B5P8CclJX/mzp4MA ksDou27z+tGni/iEjN4E0/VRIensFvWr9Ne5KUaQKTqKcOnua0yCC0buZ1wAD5N6 BU3kmLVuYsGLHPJ0MCxs0xHeVDVvaQzK5RahmI1DMg6zLRmowsI2opX6Ptxi2htn SWl87Y4Xt7DvFFM20iEHiNKPacl+CkOFDbVRZ3AjudcUVuPatUAqmWbZvnfkCTuz 1C/dHKmG2xENFoOrEcnHLdPF61QRD6JdyWql9PxcnFQaBo9xo9KueQy4/yF1Ekoo 7HUI6fdEiUT90+wjRBMEm+fQcz9jS+f4Ze7Ln6CYy74Wtf8bJ4prmCFhodh3wcz9 iLgHczYg54JIDimxcfMKXBWW7jy5MQd/bhZ5f2+4gUQsWKVZgLjnExX0GmM5NPBJ vbCmBhjD/dcPcSSZ7SoIX++RjRAX1s7JlW03AM/OFeEZyb6E3QRAvmGDjoB39fqi BMMOr5Zi/ZkR7huYSzpYt0P46qYSuQYI5GzI+Kq+T3NpbDAXULE=
=9k3h
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

El Tue, 5 Oct 2021 09:56:30 +0200
Sebastian Ramacher <sramacher@debian.org> escribió:

On 2021-09-05 15:19:33 +1000, Jai Flack wrote:

Hello,

What's the best place to put bundled Vim plugins now that vim82 has a
new package system? From the documentation,
/usr/share/vim/vim82/pack/ is the global directory for such plugins
(and I have confirmed it works correctly) however, Lintian complains
about the location.

Should I still place them according to how vim-plugin-manager
expects?

Based on what the (neo)vim maintainer has done with vim-scripts, vim-plugin-manager is being phased out. I haven't seen any efforts to coordinate a transition to vim's packaging system, but I suppose
looking at vim-scripts is a good starting point on how to install
plugins for both vim and neovim.

Cheers

Indeed, the preferred way is now to use dh-vim-addon[1] to package vim
plugins.

A couple of recent examples I have been involved with using it can be
found at vim-solarized[2], and vim-toml[3], as reference.

1: https://salsa.debian.org/vim-team/dh-vim-addon
2: https://salsa.debian.org/vim-team/vim-solarized
3: https://salsa.debian.org/vim-team/vim-toml

-Marco

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3urezGOSkdOzqEQmKhHVXGuvyhIFAmFmK7cACgkQKhHVXGuv yhKtTw/+IGdYxMnfuBcVvqxf+jPX0+6mSM+WgeWqYwLsndSVp2n1JqFG0r/tq0ef ROi+jQ4fVzDWtcdszDZ0+oQ+41Aeei7VeypbpkCmsNClMbBwWXBkeVTpFOu2r7rI wrMyfQ90VyYA5xoYqdYW5Zh0IluQL9oxSgOr1CAeWGEtiCLYR6fue78YQ3XdEnl8 uUFeof26/cVAtJM7delPIfQlNTZqi620o+2+h0STfL9nA4YB3sz5E24E9rjbIUrR hSa4XII433ZzvAsa/vUP1X7h/ovHgV+X+11ZmJPcB5XvDrmxr5OEbQV4iiG16Wod +rn5HWAmaW62EUTbh/QvfreET7JLocB3wJtk6vmkZtTzd1A5AasjRKv3ngkOy1hw H3A2fpLOPZn7qxKzMUXBYjOibIlqn17dZGFVJaXVuYF6kvB+AYAh9A8/wK8DVFgl ojQ/6SSwFm1Bo5u1ObNCHG1oMNoisAR9RWhrt8QvWekQmJ8/daZ/swGiQZNILrsA UGzMx4qC4LszdG0WOBn6FGViLtiNgspvQRom1aNt4XEyl8VnG4GeIqaGaTngieD+ ek9eUxSOO9lNi924StsVsQuS+09ez/EzUcZUno9FCycoeGWCrinGe+XNDmefGa9M qeTDN20aCd0yGsED/kF1ApGiDevw2Yrwt2Z55g9x9VdcElsi8ek=
=DNGl
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)