Dear Louis-Philippe, The first packaging I did (not published) was using `vim-addon-manager`. Although I switch to dh-vim_addon (and friends) which is not using `vim-addon-manager` anymore. This move has been recommended by James McCoy <james...@debian.org> (who sponsored the package).
I guess you spotted a lack of documentation/policy for this new helper: `dh-vim_addon`. I add James in CC. Maybe should we discuss/write a new Policy and/or some guidelines. I already started a TODO list of checks for new/next vim addon packages. I would appreciate some feedback on it, but first let me a few days to make it clean. Here are some additional notes about your comments: > It appears this package doesn't follow the Debian vim policy [1]. It's > clearly not easy to find (I had to search quite a bit to find it), but I > think it's important vim packages try to respect it :) Is this policy still relevant ? Already mentionned above. > * the addon is enabled after the installation; it shouldn't If I well understood James' advices: with `dh-vim_addon` help, vim addon packages should always be enabled if you can disable them through your vimrc with `let g:loaded_gitgutter = 1`. > * the package doesn't depend on "vim-addon-manager" like other vim plugins do It should not anymore, thanks to dh-vim_addon helper. -- Raphaël Medaer
