From: "Olivier Crête" <tester@gentoo.org>
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 17:24:52 -0700 [thread overview]
Message-ID: <1344903892.1991.4.camel@TesterTop4> (raw)
In-Reply-To: <CAJ0EP41=ttN0c_OEzfAsyiSrGYfNF1G_rME=yCfqwsk+Qw82Kg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On Mon, 2012-08-13 at 17:56 -0400, Mike Gilbert wrote:
> On Mon, Aug 13, 2012 at 2:29 PM, Alexandre Rostovtsev
> <tetromino@gentoo.org> wrote:
> > On Mon, 2012-08-13 at 11:14 -0700, Diego Elio Pettenò wrote:
> >> Beside the fact that these would probably have looked better in
> >> /usr/libexec
> >
> > See Kay Sievers's comment at
> > https://bugs.freedesktop.org/show_bug.cgi?id=51617 :
> >
> > "/usr/lib/<pkgname>/ is a directory like /usr/libexec/ or even /bin. It
> > shares absolutely zero things with the arch-specific $libdir ,or lib64/.
> >
> > /usr/lib/<pkgname>/ is the canonical "application private directory". It
> > has the multi-lib or arch-specific rules as /bin.
> >
>
> So... where should GRUB2 be installing its modules? Currently they get
> installed in /usr/$(get_libdir)/grub/$cpu-$platform, where cpu and
> platform are determined by use flags.
>
> Should we drop the get_libdir and put them in /usr/lib/grub instead?
> Should I even worry about it?
There really have no reason to be in $(get_libdir) as they're not
compiled for the platform implied by $(get_libdir) !
--
Olivier Crête
tester@gentoo.org
Gentoo Developer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-14 3:05 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ò
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 [this message]
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=1344903892.1991.4.camel@TesterTop4 \
--to=tester@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