[gentoo-amd64] Files installed to /lib or /usr/lib?

[gentoo-amd64] Files installed to /lib or /usr/lib?

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

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?


Thanks,
  Sven


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-amd64] Files installed to /lib or /usr/lib?

[Daniel Gryniewicz]

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.

Daniel

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Files installed to /lib or /usr/lib?

[Olivier Crête]

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

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
tester@gentoo.org
Gentoo Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]