From: Matthias Schwarzott <zzam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: rfc: libexec directory inconsistency
Date: Sun, 24 Apr 2011 22:38:13 +0200 [thread overview]
Message-ID: <201104242238.13811.zzam@gentoo.org> (raw)
In-Reply-To: <20110424214947.469feebf@pomiocik.lan>
On Sonntag, 24. April 2011, Michał Górny wrote:
> On Sun, 24 Apr 2011 21:43:16 +0200
>
> Matthias Schwarzott <zzam@gentoo.org> wrote:
> > Sounds like we should fix udev ebuild and some ebuilds installing
> > udev rules to not use /$(get_libdir)/udev, but plain /lib/udev.
> >
> > I used that in believe that /lib is identical or links
> > to /$(get_libdir) and multilib-strict requires it, but it seems to be
> > intelligent enough to only deny 64-bit libs to go to /lib.
> >
> > So proper udev should use /lib/udev, correct?
>
> Do you really think it'd be fine for some systems to possibly
> have /lib64 and /lib with random different contents?
Well I was always under the impression that /lib64 and /lib did point to the
same directory.
Is the case where /lib is no symlink to /lib64 so frequent?
Matthias
next prev parent reply other threads:[~2011-04-24 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 17:02 [gentoo-dev] rfc: libexec directory inconsistency William Hubbs
2011-01-22 19:26 ` [gentoo-dev] " Diego Elio Pettenò
2011-04-24 19:43 ` Matthias Schwarzott
2011-04-24 19:49 ` Michał Górny
2011-04-24 20:38 ` Matthias Schwarzott [this message]
2011-04-26 6:38 ` Michał Górny
2011-04-26 5:06 ` Matthias Schwarzott
2011-04-24 20:08 ` Samuli Suominen
2011-04-24 20:30 ` Matthias Schwarzott
2011-04-30 12:30 ` [gentoo-dev] Re: udev installs now to /lib/udev (was: rfc: libexec directory inconsistency) Matthias Schwarzott
2011-01-23 3:17 ` [gentoo-dev] rfc: libexec directory inconsistency Mike Frysinger
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=201104242238.13811.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=gentoo-dev@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