On 16/11/17 00:20, James McCoy wrote: > On Wed, Nov 15, 2017 at 10:15:31AM -0700, Sean Whitton wrote: >> On Wed, Nov 15 2017, James McCoy wrote: >> >>> One thing I'd like to note is that none of the vim-$lang virtual >>> packages are currently listed in Policy's set of virtual packages. >>> That was an oversight on the Vim maintainers side when the package >>> names were introduced, but maybe now would be a good time to correct >>> that. >> >> The point of listing virtual packages in Policy is to deal with >> disparate people maintaining packages that Provide the virtual package. >> If the people using the virtual packages are part of a tightly-knit >> packaging team, they can maintain the virtual packages themselves, >> without listing them in Policy. > > Ok. I had 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, >
I'm ok too with it being out of policy. We can close this vim-python3 bug (#881633) and the vim-python one (#881642), then. Cheers, -- Víctor Cuadrado Juan m...@viccuad.me PGP key ID: 4096R: 0xA2591E231E251F36 Key fingerprint: E3C5 114C 0C5B 4C49 BA03 0991 A259 1E23 1E25 1F36 My signed E-Mails are trustworthy.
signature.asc
Description: OpenPGP digital signature
