On Fri, Jan 12, 2007, Steve Langasek wrote: > If you're going to use non-standard paths at all, why would you not move > this to /usr/lib/i486-linux-gnu, which is also already part of the system > lib path in etch and is much better future-proofed than the alternatives?
I'm willing to use whatever is blessed by bi-arch as I think it would make sense to support bi-arch in the lenny lifecycle; I think the adaptation that libpango needs are relatively close in both cases (but biarch will need a second build of course). (FYI, pango can be built with multi-arch support but /usr/lib/i486-linux-gnu, is then used as libdir, not just for module files and modules.) It seems to me 64-bits libs for i386 use /usr/lib64 in bi-arch (I checked lib64z1 and lib64asound2). It's less clear to me what to use for 326bits libs on 64-bits arches: lib32z1 and lib32asound2 use /emul/ia32-linux/usr/lib; is this correct? Does it make sense that use this path? -- Loïc Minier <[EMAIL PROTECTED]>
