[Build-common-hackers] Bug#587240: Bug#587240: example
dr at jones.dk
Sun Jun 27 08:55:53 UTC 2010
On Sun, Jun 27, 2010 at 02:13:38AM +0200, Steffen Möller wrote:
>I run into this issue for everything that I package with
>python-central. The python-support-run packages don't seem to be
>affected. When you look up to the patch a bit, you see that in only
>changes site-packages to dist-packages for the installation, and only
>if the version of python is 2.6 or higher. The Debian Python Policy
>almost verbatim states this on
>section 1.5 "Module Path".
I know about Policy. I just believed that it was already magically
taken care of, but now, double-checking with the Python packages I am
involved in myself, I see that they either are arch-independent or use
Autotools (not distutils).
I did wonder in the past how that explicit path in distutils.mk was so
magically handled correctly also with Python 2.6 and apparently it
really isn't after all. Your patch looks good and I'll apply it.
Thanks a lot!
>You asked for an example, well, I don't really want to show those
>publicly yet, but I ran into this (and wasted half a day (with breaks)
>over it) while packaging python-nast (or should it be python-pynast?)
>that depends on python-cogent. You can see all the files on
Yes, I do believe the package should be named python-pynast, as its
contained module (the __init__.py dir) is called pynast.
>Has this helped?
Providing that concrete example og python-nast indeed helped open my
eyes to the (obvious!) problem. :-)
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: Digital signature
More information about the Build-common-hackers