Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit : > Pierre Habouzit (madcoder@debian.org): > > well the thing is there is no way to track all the packages that > > *have* to follow the python subpolicy, and that makes the work of > > tracking them for transition harder. > > > > I think/thought it makes sense that a source package lists all the > > subpolicies it's supposed to follow, because it makes our lifes > > easier. > > You can't bump Standards-Version number if your package is not > following *all* standards (i.e subpolicies). > > The fact is that python policy is not official yet (at least document > on d.o is not updated) and > /usr/share/doc/debian-policy/upgrading-checklist.txt.gz > doesn't mention about new python policy at all. we are not talking about the same target. My goal is to be able to spot every package that has to conform to the python subpolicy by just listing those fields. Obviously the Standards-Version is bumped also, but it's not distinctive of python and not python related packages. Thouth I think it's handy, but it's not more than a suggestion, I don't really care about that. -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgp5qnEHCesOU.pgp
Description: PGP signature