On Tue, Jul 11, 2006, Loïc Minier wrote:
> Or should pyexecdir be dropped from .pc files?
After some IRC discussion, this is not an option, and would violate the
contract between the upstream .pc file authors and the upstream
application developers trying to use these .pc files.
Some other ideas revolving around pkg-config file syntax:
<module>.pc:
pyexecdir_python2.3=${exec_prefix}/lib/python2.3/site-packages
pkg-config --variable=pyexecdir_python2.3 <module>
<module>.pc:
pyexecdir=${exec_prefix}/lib/${python}/site-packages
pkg-config --define-variable=python=python2.4 --variable=pyexecdir <module>
pkg-config --variable=pyexecdir <module>
Or use a <module>-pythonXX.pc scheme.
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.
In the past, we would have had multiple -dev packages, conflicting with
each other, but it's quite hard with the new pyversions stuff.
Bye,
--
Loïc Minier <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
