public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: libexec directory inconsistency
Date: Sat, 22 Jan 2011 22:17:29 -0500	[thread overview]
Message-ID: <AANLkTiku-R-wCPrSzF6MCJarSNiNPFLSfJZsbhdqXchN@mail.gmail.com> (raw)
In-Reply-To: <20110122170242.GA17407@linux1>

On Sat, Jan 22, 2011 at 12:02 PM, William Hubbs wrote:
> 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.
>
> I enquired from Robin why we do this, and I was told that libexec is
> supposed to contain things which are not abi specific, but we do not
> enforce that for /, even though we do for /usr.
>
> Is there a reason for this? If not, would it break things if we start
> using /libexec as well as /usr/libexec?

/libexec is also a horrible wart which we have avoided on purpose.
*BSD systems might use it, but we dont in Linux.

i dont think the multilib issue is terribly relevant unless the files
in question are used externally.  with dhcpcd and openerc, the files
are only used internally, so keeping them in the native multilib dir
isnt an issue.
-mike



      parent reply	other threads:[~2011-01-23  3:18 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
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 ` Mike Frysinger [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=AANLkTiku-R-wCPrSzF6MCJarSNiNPFLSfJZsbhdqXchN@mail.gmail.com \
    --to=vapier@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