"Josselin Mouette" <j...@debian.org> wrote:
>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.
>
>> 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.
>
If there is concurrence from the release team that there is no need to expose
this externally then I don't see a need to require it. It would be part of a
tool set, but up to the package maintainer if they use it.
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/e318c32f-76fb-43ce-9e5b-9985f0392...@email.android.com
