On Sat, Oct 20, 2012 at 06:01:24PM +0200, Matthias Klose wrote: > right, many packages assume to find the python headers in exactly one > directory.
> $ python3.3-config --includes > -I/usr/include/python3.3m -I/usr/include/x86_64-linux-gnu/python3.3m > this could be fixed by moving all the python headers into the multiarch > directory, however that's not that what multiarch proposes to do. Multiarch allows headers to be shipped in either a common /usr/include directory or in a per-architecture include directory, as needed and as appropriate. Just as we may ship architecture-independent files in /usr/lib/$pkg that are closely related to the architecture-dependent files in the same directory for convenience, we can ship architecture-independent headers in /usr/include/$arch if that works best for the software using these headers. It may waste some disk space, but that should be weighed against the work of fixing all software to handle the split headers. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
-- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
