On Tue, 08 Sep 2009 11:49:20 +0200 Bernd Zeimetz <be...@bzed.de> wrote: >Steve Langasek wrote: >> The XS-Python-Version field was specified as a tool for detecting, without >> having to download and inspect individual source packages, that a given >> package can be successfully rebuilt for a python transition, to aid the >> release team in this work. > >As mentioned somewhere else in this thread it makes much more sense to loog at >the build-dependencies. Packages which need a special (single) version of Python >are easy to detect on their biuild-dependencies. For the few packages which >depend on python-all(-.*), although they build modules only for a limited number >of Python versions, it is still a good idea to rebuild them to ensure that they >still build with the tools from the latest version (like pyversions, python.mk, >your $favourite python helper). >>From the 90 packages in the Python Modules team which use debian/pyversions, >there are only 5 which have the Python versions limited to <<2.5, so they'll be >gone as soon as Python 2.4 is removed. >So I fail to see a reason why the XS-Foo stuff is necessary. > Does pyversions offer any real advantages over XS-...? All things being equal, if both helpers support a common method for this I think we should just use it.
Scott K P. S. Despite most of my packages currently using one helper, I'm not dogmatic about it. I'm mostly sick of all this mess. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
