Hello,
as you may have read in the previous mail, the latest dh_python uses
a debian/pyversions file to find out the Python versions that the
packages supports but uses as fallback the XS-Python-Version field in
order to not break compatibility with packages that have already been
updated.
For that I've written code in dh_python that re-creates the content of
debian/pyversions from the XS-Python-Version field. However it's now quite
clear that this XS-Python-Version field is only essential for
python-central and as such keeping that compatbility code inside dh_python
may be breaking the rule that dh_python tries to be agnostic (and which is
the wish of Joey Hess also).
So I wonder if I should move that code from dh_python to dh_pycentral and
make dh_pycentral create the debian/pyversions file that would then be
used by dh_python as external input.
What do you think, would you do that or would you keep it in dh_python?
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
