On Wed, Oct 12, 2011 at 12:50:32PM +0200, Cyril Brulebois wrote: > Adam Borowski <firstname.lastname@example.org> (12/10/2011): > > On Wed, Oct 12, 2011 at 06:56:25AM +0000, Philipp Kern wrote: > > > On 2011-10-11, Ognyan Kulev <email@example.com> wrote: > > > > > > > > /usr/include -> /usr/share/include > > > > > > Obviously broken. Includes can (and will be) architecture-specific. > > > > With multiarch, they are shareable. > > /usr/share is not where architecture-specific stuff goes. With or > without multiarch. Currently it's not, but this very thread is about moving things around. What I mean is, there is no reason to consider these files to be unshareable. Just like, say, win32 libraries which are arch-specific (and an arch alien to Debian!) yet can be used by wine:amd64, wine:i386 or wine+qemu:armel just the same. I wouldn't be too hasty in doing that move -- a system-on-NFS setup that shares different architectures is quite a bizarre exercise, not worth to put too much effort into. Yet the same step of multiarch that allows cross-compilation also makes such a setup possible. -- 1KB // Yo momma uses IPv4!
Description: Digital signature