On Tue, Jul 11, 2006, Loïc Minier wrote:
> It's also possible to influence the PKG_CONFIG_PATH, eg.
> PKG_CONFIG_PATH=/usr/lib/pkg-config/python2.3:$PKG_CONFIG_PATH in
> debian/rules.
I tried this, and it wasn't too hard except it needed a "rtupdate"
script to update the symlinks after a default python runtime change,
and the symlinks need to be created / removed in postinst / prerm.
However, I just discovered it does only fix some use cases. From
gst0.10-python's configure.ac:
PKG_CHECK_MODULES(PYGTK, pygtk-2.0 >= $PYGTK_REQ)
=> (ok, that will now work)
PYGTK_DEFSDIR=`$PKG_CONFIG --variable=defsdir pygtk-2.0`
=> (/usr/share/pygtk/2.0/defs: I can only ship that one time)
PYGTK_H2DEF=`$PKG_CONFIG --variable=codegendir pygtk-2.0`/h2def.py
PYGTK_CODEGEN="$PYTHON `$PKG_CONFIG --variable=codegendir
pygtk-2.0`/codegen.py"
=> (/usr/share/pygtk/2.0/codegen/h2def.py and codegen.py: same problem)
So, am I supposed to install every file below a directory versionned
with the python runtime and handle symlink creation, deletion, and
updates in maintainer scripts? (These dirs are not ./configure-able.)
--
Loïc Minier <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
