[Debian-med-packaging] Bug#516766: insighttoolkit: generates incorrect package with python-support from experimental
joss at debian.org
Sun Mar 8 04:27:33 UTC 2009
Le samedi 07 mars 2009 à 22:17 -0600, Steve M. Robbins a écrit :
> OK. I'm certainly in favour of avoiding complexity. However, I
> thought I was following the python policy  where B.1 says:
This document is incorrect. Since it is basically unmaintained and
contains many similar mistakes, you should especially not rely on it.
> When using python-support, you should install your modules to
> /usr/share/python-support/package rather than the standard Python
Note that this will go on working in the general case, but not for two
* packages installing files in /usr/lib/python-support by hand;
* packages modifying files in /usr/share/python-support *after*
the call to dh_pysupport.
Both of these cases represent most of the issues with the move
> Where should I be installing the .py files?
> Where should I be installing associated .so files?
You should install all of them to /usr/lib/pythonX.Y/site-packages, as
distutils does by default. Their being moved
to /usr/share/python-support (or /usr/share/pyshared for the
experimental version) is handled by dh_pysupport.
As for InsightToolkit, you should also ask yourself whether these
modules really need to be made public, or if it would be simpler to ship
them in a private directory like the upstream installer does.
.''`. Debian 5.0 "Lenny" has been released!
: :' :
`. `' Last night, Darth Vader came down from planet Vulcan and told
`- me that if you don't install Lenny, he'd melt your brain.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Ceci est une partie de message
Url : http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20090308/5aec4ce1/attachment.pgp
More information about the Debian-med-packaging