On 2020-07-09 12 h 37, Raphael Medaer wrote: > 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.
No idea, I'm only a vim user and I haven't done any vim work in Debian :) > > > * 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`. This is quite a big change and I guess it breaks my current setup :s I feel this should be publicized and done in coordinated fashion for all the vim packages in preparation for Bullseye. Having a mix of the two behaviors (enabled and disabled by default) sounds like headache. I don't mind moving to something else, but I quite like being able to use vim-addon-manager as a frontend for vim addons. It would be nice if the new packaging guidelines made it somehow possible to continue using that tool. Cheers! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
signature.asc
Description: OpenPGP digital signature
