On mer, 2008-01-16 at 20:18 +0100, Joop Stakenborg wrote:
> >       * The Debian build process only builds the package for one python
> >         version; this way the module built for python2.4 will not work
> >         with python2.5. You must loop over the supported python versions
> >         to build the module for each of them, and install it in each of
> >         the corresponding /usr/lib/python2.X/site-packages directories.
> >
> 
> This means I will need to build all of the hamlib related packages for
> the different python versions in Debian (I need to start the build
> process all over again for every python version). There is no way in
> the hamlib source to only build the python module. This isn't very
> elegant.

Indeed. I think you could hack around that by something like that:
        $(MAKE)
        for pyvers in $(PYVERS); do \
                $(MAKE) -C bindings clean ; \
                PYTHON=python$(pyvers) ./configure $(configure_flags) ;\
                $(MAKE) -C bindings ;\
                mv bindings/_Hamlib.so bindings/_Hamlib.py$(pyvers).so ;\
        done

and then install every _Hamlib.py*.so in the
relevant /usr/lib/python*/site-packages directories.

> > There are examples of how to do that in the python-support documentation
> > and on the wiki. If you need help, please don't hesitate to ask for a
> > patch.
> >
> 
> I have looked over the docs and wiki a couple of times. It is hard to
> understand for a python outsider. There are so many issues, it's all
> very confusing.

Unfortunately, many docs are trying to make things look complicated
while they are not. Except for some rare cases, the only things that can
really be an issue are to specify the supported python versions and to
build the package for all python versions. All the rest should be dealt
with by the debhelper scripts.

> So, yes a patch would be very much appreciated to have this resolved!

Here is a simple version that rebuilds everything for all python
versions.

BTW, there seems to be a lot of other issues with the package; having a
simple look at the list of lintian errors is scary enough. Not talking
about the incorrect emptiness of the binary-indep target, or the
unnecessary complexity of installing everything by hand.

Cheers,
-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

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

Reply via email to