From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: rfc: libexec directory inconsistency
Date: Sun, 24 Apr 2011 23:08:02 +0300 [thread overview]
Message-ID: <4DB48322.2050307@gentoo.org> (raw)
In-Reply-To: <201104242143.17576.zzam@gentoo.org>
On 04/24/2011 10:43 PM, Matthias Schwarzott wrote:
> Getting that discussion back on top.
>> Which is wrong, it should be /lib/foo instead, not $(get_libdir), to
>> follow what udev and other software in Linux has been using for a very
>> long time now.
>
> Sounds like we should fix udev ebuild and some ebuilds installing udev rules to
> not use /$(get_libdir)/udev, but plain /lib/udev.
Right, doesn't make sense to have both 32bit and 64bit ELF's for udev,
so we should stick with /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?
Correct.
The udev situation is really a mess tree-wide, we have ebuilds
installing into 3 different directories now:
/etc/udev (where user puts his local rules)
/$(get_libdir)/udev (as explained above)
/lib/udev (the correct one)
Check the Portage to see the sad status of inconsistency:
$ grep -r 'etc.*udev' */*/*.ebuild
$ grep -r 'get_libdir.*udev' */*/*.ebuild
next prev parent reply other threads:[~2011-04-24 20:07 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
2011-04-26 6:38 ` Michał Górny
2011-04-26 5:06 ` Matthias Schwarzott
2011-04-24 20:08 ` Samuli Suominen [this message]
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=4DB48322.2050307@gentoo.org \
--to=ssuominen@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