On Mon, Feb 23, 2009 at 04:16:50PM +0100, Josselin Mouette wrote: > the insighttoolkit rules file contains the following: > > PYMODDIR = usr/share/python-support/$(pkg_python) > PYEXTDIR = usr/lib/python-support/$(pkg_python)/$(PYVERS) > ... > install/$(pkg_python):: > dh_install -p$(pkg_python) -XlibSwig > debian/tmp/usr/lib/InsightToolkit/*Python.so* $(PYEXTDIR) > dh_install -p$(pkg_python) > debian/tmp/usr/lib/InsightToolkit/libSwigRuntimePython.so* usr/lib > dh_install -p$(pkg_python) debian/tmp/usr/lib/InsightToolkit/python/* > $(PYMODDIR) > dh_install -p$(pkg_python) debian/tmp/usr/lib/InsightToolkit/*.py > $(PYMODDIR) > dh_pysupport -p$(pkg_python) > > With the upcoming version of python-support (currently in experimental), > the files installed in /usr/lib/python-support are ignored and the built > package is, as such, broken. > > You should install these packages to a standard place instead of adding > all this complexity. Then, dh_pysupport will pick them and do whatever > is fit.
OK. I'm certainly in favour of avoiding complexity. However, I
thought I was following the python policy [1] where B.1 says:
When using python-support, you should install your modules to
/usr/share/python-support/package rather than the standard Python
directories.
Where should I be installing the .py files?
Where should I be installing associated .so files?
Thanks,
-Steve
[1]
http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html#s-pysupport
signature.asc
Description: Digital signature
