On Thu, Jan 11, 2007, Goswin von Brederlow wrote: > Replacing the /usr/lib/pango/1.5.0/module-files.d/* with > /usr/lib32/pango/1.5.0/module-files.d/* fixes this problem for 32bit > but obviously breaks 64 bit.
Can we use /usr/lib32 in all cases or should we use /usr/lib32 only for the pango embedded in ia32-libs? IOW, can I change the pango/i386 package to ship /usr/lib32/pango/1.5.0/module-files.d and the the pango/amd64 package to use /usr/lib64/pango/1.5.0/module-files.d -- and hence have no /usr/lib/pango/1.5.0/module-files.d except on other arches (m68k, arm, ...)? Is it more useful to turn on the support for /usr/lib32 at runtime only, or is it ok to unconditionally setup this support at build time? -- Loïc Minier <[EMAIL PROTECTED]>
