On Tue, 22 Aug 2006, Brian Sutherland wrote: > On Tue, Aug 22, 2006 at 12:42:03AM +0200, Josselin Mouette wrote: > > Le mercredi 16 ao?t 2006 ? 11:34 +0200, Brian Sutherland a ?crit : > > > It seems to me that dh_python should set Python-Version to x.y if > > > XS-Python-Version is x.y regardless of what the current default python > > > is. At least that is what I would have expected. > > > > This is one of the reasons why I don't like the X?-Python-Version > > fields. There is no way for the build process to tell between those two > > cases: > > 1. building for python2.4 only as we build for one version only and > > python2.4 is the default version; > > 2. building for python2.4 only as this is the only supported > > version. > > Does this not work for case 1: > > XS-Python-Version: current > > and for case 2: > > XS-Python-Version: 2.4
Yes it should. It's solely a dh_python bug... and not really a design issue with the field as Joss thinks. I could create a patch for it but as Joey wants to remove dh_python altogether, I try to make it happen by moving what's required to dh_pycentral/dh_pysupport instead of fixing something that will go away. (If only Joey had been a bit more involved when the discussion on python policy was live he could have advised me to create a library for dependency generation from the beginning instead of letting me use dh_python. And at that time, I would have had no problem pushing it into python-support/python-central.) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
