Hi, On 01.08.2016 22:35, Gianfranco Costamagna wrote: > it is good, just called "3.0.2-2" > > please use -1 as versioning and dput -f on mentors until it gets accepted. >
Ah ok, sorry. :-) I removed the package and uploaded it again as 3.0.2-1 . > last thing: how do I enable such extension? In the vim-policy[1] by the vim package team they recommend to use vim-addon-manager. That means, install the debian package vim-addon-manager (which is recommended by the vim-lastplace package) and then execute "vim-addons install lastplace" . This copies the appropriate files from /usr/share/vim/addons/ to ~/.vim/ for that user. There is also a way to "activate" an addon system wide via "vim-addons -w install lastplace", which copies the files to /var/lib/vim/addons . This seems to be a little inconvenient, but with multiple addons installed and multiple users of which everyone wants to configure which addon to use, it is probably the cleanest solution. I have seen that for example the vim-tabular package handles this via preinst and postinst scripts to "activate" the addon system-wide by default. The user can still disable it by "vim-addons disable vim-tabular". Handling it this way is however discouraged by [1]. But maybe in our case it makes sense to do it like this as well. Because if someone installs a package with exactly one vim addon he or she probably wants it to be enabled by default. (Unlike for example when installing the package vim-scripts, which contains multiple vim addons.) But in the Debian New Maintainers' Guide they say "As a novice maintainer, you should avoid any manual editing of maintainer scripts because they are problematic.", so maybe it is good as it is right now. :-D Regards, David [1] https://pkg-vim.alioth.debian.org/vim-policy.txt
signature.asc
Description: OpenPGP digital signature
