From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] FYI: multilib-strict no longer in FEATURES of targets/developer/make.defaults (pending on bug 424423)
Date: Mon, 13 Aug 2012 14:24:04 -0700 [thread overview]
Message-ID: <50297074.1030502@flameeyes.eu> (raw)
In-Reply-To: <1344882542.23246.3.camel@rook>
On 13/08/2012 11:29, Alexandre Rostovtsev wrote:
> "/usr/lib/<pkgname>/ is a directory like /usr/libexec/ or even /bin. It
> shares absolutely zero things with the arch-specific $libdir ,or lib64/.
Yes I know that FHS allows it. I still think it would be cleaner to use
/usr/libexec.
It's the usual difference between trying to be right and being pragmatic
about it.
You (and Kay) want to be right ignoring the fact that $tons of software
expects /usr/lib to just be another $libdir.
I'd rather be pragmatic and choose /usr/libexec which _clearly_ isn't.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
next prev parent reply other threads:[~2012-08-14 0:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 16:55 [gentoo-dev] FYI: multilib-strict no longer in FEATURES of targets/developer/make.defaults (pending on bug 424423) Samuli Suominen
2012-08-13 18:14 ` Diego Elio Pettenò
2012-08-13 18:29 ` Alexandre Rostovtsev
2012-08-13 21:24 ` Diego Elio Pettenò [this message]
2012-08-14 9:57 ` Samuli Suominen
2012-08-14 13:35 ` Diego Elio Pettenò
2012-08-14 16:57 ` Samuli Suominen
2012-08-14 17:07 ` Samuli Suominen
2012-08-14 17:13 ` Diego Elio Pettenò
2012-08-14 14:05 ` Michał Górny
2012-08-14 17:05 ` Samuli Suominen
2012-08-14 17:05 ` Samuli Suominen
2012-08-13 21:56 ` Mike Gilbert
2012-08-14 0:24 ` Olivier Crête
2012-08-14 10:01 ` Samuli Suominen
2012-08-13 18:25 ` Rick "Zero_Chaos" Farina
2012-08-14 17:03 ` Samuli Suominen
2012-08-14 17:37 ` Alexis Ballier
2012-08-18 3:43 ` 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=50297074.1030502@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--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