"Josselin Mouette" <j...@debian.org> wrote:
>Le mercredi 23 juin 2010 à 13:15 -0400, Scott Kitterman a écrit :
>> 1. Use XS/B-P-V for Python and Python3 versions
>> 2. Create a new set of fields, XS/B-Python3-Version.
>> 3. Create a new field, X-Python-Version: for Python3 versions.
>> 4. Create a new field, X-Python3-Version: for Python3 versions
>
>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.
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.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/44796d70-2a7e-41ae-a736-7078f5779...@email.android.com
