On Thu, 2006-06-15 at 13:44 +0200, Pierre Habouzit wrote:
> Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit :
> > Pierre Habouzit ([EMAIL PROTECTED]):
>
> > > 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
Pierre Habouzit ([EMAIL PROTECTED]):
> 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
Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit :
> Pierre Habouzit ([EMAIL PROTECTED]):
> > 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
Pierre Habouzit ([EMAIL PROTECTED]):
> Le jeu 15 juin 2006 10:50, Piotr Ozarowski a écrit :
> > I think a better idea is to use Standards-Version as we did before
> > (version 3.8.0 should be released)
>
> well the thing is there is no way to track all the packages that *have*
> to follow the pyt
Le jeu 15 juin 2006 10:50, Piotr Ozarowski a écrit :
> Pierre Habouzit ([EMAIL PROTECTED]):
> > I'd like to suggest a last minute amendment to the Python Policy,
> > that would help further transitions a lot. I'd suggest that
> > packages uses a XS-Python-Standards-Version, that would'nt be
> > man
Pierre Habouzit ([EMAIL PROTECTED]):
> I'd like to suggest a last minute amendment to the Python Policy, that
> would help further transitions a lot. I'd suggest that packages uses a
> XS-Python-Standards-Version, that would'nt be mandatory for the current
> policy but *strongly* advised (a foll
6 matches
Mail list logo
