a recollection of that.
>
>> In light of this, could you confirm that this needs to go into Policy?
>> I am not familiar with you Vim guys, what with being the co-maintainer
>> of a dh_* tool for Emacs addons..
>
> I don't think so. Victor?
>
> Cheers,
>
On Mon, 13 Nov 2017 19:34:44 +0100 Víctor Cuadrado Juan wrot>
It will allow vim python3 plugins to require on it.
Expanding on the rationale:
vim works with python2 and python3 plugins simultaneously. Those vim python
plugins depend on the vim-python virtual package.
In the case of neo
t (with the proper changes in the explanation entry).
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881633
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881642
[3]: https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt
Kind regards,
--
Víctor Cuadrado Juan
Package: debian-policy
Version: 4.1.1.1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
while opening the debian-policy wishlist bug [1] about creating a vim-python3
package, I've noticed that the existing `vim-python` package is not in the list
of virtual packages main
Package: debian-policy
Version: 4.1.1.1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Following steps in [1], here is the wishlist bug for creating
a `vim-python3` virtual package, homologous to the already present
`vim-python` virtual package.
It will allow vim python3 plug
5 matches
Mail list logo
