public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Olivier Crête" <tester@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Files installed to /lib or /usr/lib?
Date: Fri, 13 Jul 2007 17:04:48 -0400	[thread overview]
Message-ID: <1184360688.6448.25.camel@localhost> (raw)
In-Reply-To: <1184359928.22061.101.camel@athena.fprintf.net>

[-- 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 --]

      reply	other threads:[~2007-07-13 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 20:01 [gentoo-amd64] Files installed to /lib or /usr/lib? Sven Köhler
2007-07-13 20:52 ` Daniel Gryniewicz
2007-07-13 21:04   ` Olivier Crête [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1184360688.6448.25.camel@localhost \
    --to=tester@gentoo.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox