Le jeudi 11 octobre 2007 à 11:44 +0200, Peter Eisentraut a écrit :
> Am Donnerstag, 11. Oktober 2007 schrieb Josselin Mouette:
> > Le mardi 09 octobre 2007 à 13:52 +0200, Peter Eisentraut a écrit :
> > > Am Montag, 8. Oktober 2007 schrieben Sie:
> > > > Well, that of course depends on what's inside the package. If it is
> > > > able to work with both python versions, a dependency on "python-dev,
> > > > ${python:Depends}", leading to "python-dev, python (>= 2.4), python (<<
> > > > 2.6)" should do the trick.
> > >
> > > That doesn't do the same thing.  I need a dependency on python2.4-dev,
> > > which the above doesn't imply.
> >
> > The above implies python2.4-dev while 2.4 is the default, and
> > python2.5-dev when 2.5 becomes the default. Which is exactly what you
> > need, unless I have again missed something.
> 
> No, I need a dependency against the -dev package belonging to the python 
> version against which the package was originally built.

First of all, in all cases you must not make this dependency hard-coded
unless there is really something that only works with python 2.4.

AIUI you are hardcoding python 2.4, telling yourself that you will
change that to 2.5 when it becomes the default. And doing that, you will
make the transition of 70 other packages depend on your work. There is a
good reason why automated python dependencies were introduced, and it is
precisely to avoid that by being able to update packages to a new python
version with only a binNMU.

The real, good solution is to build the extensions for all available
python versions. It is always possible but sometimes it can be quite
complicated. In your case, doing it for libhk-classes-dev looks tricky
because you'd have to switch the binaries with a rtupdate script, so I
understand you don't want to do that, but that doesn't prevent you from
making your package binNMUable.

In all cases, the dependency should be made dynamic, so that it
corresponds to the actual python versions your package supports.

Cheers,
-- 
 .''`.           Josselin Mouette        /\./\
: :' :           [EMAIL PROTECTED]
`. `'                        [EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée

Reply via email to