On Sunday 13 June 2010 18:37:00 Sandro Tosi wrote:
> > But that would be too much and the package would then have to be manually
> > updated every-time you upversion python.
>
> The correct way to handle it is to set XS-P-V to ">= 2.5" (that
> declares the package only works with version 2.5 onward) or even to
> "all" (that declares the package can use any of the supported version
> of Python in Debian) and then build the package for all the supported
> versions in debian/rules.
Thanks Sandro,
I have implemented this, but it is still causing issues.
> You can call pyversions (with parameters, IIRC -s for all the
> supported versions) then loop over those versions and call "python$ver
> setup.py build" and then "install" on each of them.
>
> Also, I suggest to use a python helper program, and the debian-python
> community suggests python-support, which is reliable and
> well-maintained.
We have pyversions and are using python-support, but still are not getting what
we need.
If we build the hplip package with python2.5 installed, then it places the
modules under /usr/lib/python2.5/site-packages:
http://packages.debian.org/sid/ia64/hplip/filelist
If we build the hplip package with python2.6 installed then it places the
modules under /usr/lib/python2.6/dist-packages:
http://packages.debian.org/sid/i386/hplip/filelist
The python2.5 built packages (/usr/lib/python2.5/site-packages) do not work if
python2.6 is installed, as it cannot locate the correct modules.. :-(
So how do I force depends to be set to ensure the correct version of python is
installed, or how to I ensure that either version of python will look in either
location for the modules??
Mark
signature.asc
Description: This is a digitally signed message part.
