From: "Diego Elio Pettenò" <flameeyes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: rfc: libexec directory inconsistency
Date: Sat, 22 Jan 2011 20:26:12 +0100 [thread overview]
Message-ID: <1295724372.2648.92.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <20110122170242.GA17407@linux1>
Il giorno sab, 22/01/2011 alle 11.02 -0600, William Hubbs ha scritto:
> Is there a reason for this? If not, would it break things if we start
> using /libexec as well as /usr/libexec?
More or less and yes, it would create one more root directory that has
no real usage to be there anyway...
> I noticed that for dhcpcd and openrc we force their LIBEXECDIR to be
> $(get_libdir)/foo, which puts things in different directories
> depending on whether the system is multilib or not.
>
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.
The one problem we have here is that for reason I don't know,
no-multilib profiles started using lib64 exclusively instead of the
(proper) lib exclusively...
--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
next prev parent reply other threads:[~2011-01-22 19:26 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 ` Diego Elio Pettenò [this message]
2011-04-24 19:43 ` [gentoo-dev] " 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
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=1295724372.2648.92.camel@raven.home.flameeyes.eu \
--to=flameeyes@gmail.com \
--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