On Fri, 2007-13-07 at 16:52 -0400, Daniel Gryniewicz wrote: > On Fri, 2007-07-13 at 22:01 +0200, Sven Köhler wrote: > > Hi, > > > > what's the current way of dealing with the folders /lib and /usr/lib > > which are symlinks to /lib64 or /usr/lib64 on amd64 systems? > > > > Here: https://bugs.gentoo.org/show_bug.cgi?id=185126#c3 > > one of the gentoo devs (Jakub) thought, that paths like /usr/lib > > shouldn't be hardcoded. Hmm - to me, this statement only makes sense, if > > ebuilds installing files to /lib or /usr/lib are actually disliked. > > > > But actually, very fundamental stuff like udev, grub-static, etc. > > still install there files to /lib or /usr/lib instead of /lib64 or > > /usr/lib64. > > > > So should these packages be fixed? > > Or is it intentional or at least legal, that they install files to /lib > > or /usr/lib on amd64? > > > > binary libraries should not be installed to /usr/lib or /lib (and will > fail multilib-strict checks, if they are). Anything else, such as > python files or text files, can be installed in /usr/lib and /lib.
Even then, anything that is different between architectures should be in /usr/lib<XX>. -- Olivier Crête [EMAIL PROTECTED] Gentoo Developer
signature.asc
Description: This is a digitally signed message part
