Re: Proposed Email to the release team about XS/B-P-V

[Piotr Ożarowski <piotr@debian.org>]

[Josselin Mouette, 2010-06-24]
> Le mercredi 23 juin 2010 à 21:17 -0400, Scott Kitterman a écrit :
> > >5. End this madness and use the version in build-dependencies instead of
> > >asking maintainers to specify it twice - which they usually do wrong.
> > >
> > With this approach then with the current python-defaults in Sid, how would one specify works with 2.5 and 2.6, but not 2.7?
> > 
> > b-d python{-all} (>= 2.5), python{-all} (=< 2.7)
> > 
> > Since a python-all version of 2.6 may at different times reflect b-d on 2.5, 2.6, and/or 2.7 versions, this isn't clear to me.
> 
> Indeed, but I doubt this is a real problem.

it gets a little bit messy when minimum required Python version is
greater than the default one, but it should work, yes (IIRC last year
someone gave me example where it wouldn't work, but I don't remember it
now, hopefully it will be pointed out again soon)

example for default=3.1 minimum=3.2 maximum=3.5:
 python-all | python-all (>= 3.2), python-all (<< 3.5), python-all (>= 3.1.2-2)
or even
 python-all (>= 3.1.2-2) | python-all (>= 3.2), python-all (<< 3.5)

I will implement it in dh_python3 (only ">= X.Y" and "<< X.Y" will be
taken into account, I will ignore all ".* X\.Y.*" including X.Y-Z)) and
use it if -V, debian/pyversions, X-Python-Version and XS-Python-Version
is not available (in that order)

> > Also how does that intersect with needing specific package features to
> > build (e.g python-all (>= 2.6.5-2~) because I switched from
> > python-central to dh_python2)?
> > 
> > I'd love to just specify it once if we can do it in a reasonably
> > non-convoluted and complete way.
> 
> Then at the very least, make your X-Whatever-Ugly-Hack opt-in instead of
> requiring it.

it's not required
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645