[Python-apps-team] Fwd: Re: Your measures against the FTBFS of HPLIP seem not to show any effect

[Mark Purcell]

Hey python-apps-team,

I am the maintainer for hplip which has a number of python modules.

I need to include these during build time so I can generate man pages.

I have currently hardcoded via the PYTHONPATH var, but of course that doesn't work in a mixed python 2.5/ 2.6 environments.

        ( cd ./debian/tmp/usr/share/hplip/; \
            for file in *.py; do \
                if [ -x $$file ] && [ $$file != install.py ] && \
                   [ $$file != hpssd.py ] && [ $$file != dat2drv.py ] && \
                   [ $$file != __init__.py ]; then \
                    dest=hp-$${file%.py}; \
                    ln -s /usr/share/hplip/$$file \
                        ../../bin/$$dest 2>/dev/null || :; \
                    PYTHONPATH=../../lib/python2.5/site-packages/  LD_LIBRARY_PATH=../../lib/ ../../bin/$$dest --help-man > $(CURDIR)/$$dest.1 ; \
                fi; \
            done \


What do you recommend in these situations?

Mark

----------  Forwarded Message  ----------

Mark Purcell wrote:
> I hardcoded the location of the modules during build:
> PYTHONPATH=../../lib/python2.5/site-packages/
> 
>> Somehow we must get it working under both Ubuntu and Debian.with the 
>> same code in debian/rules.
> 
> There must be a variable we can use in the debian/rules to ensure that the correct local location is set in PYTHONPATH.
-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20091207/9b532f5f/attachment.pgp>