From: Ruud Koolen <redlizard@gentoo.org>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Names of Prefix variants
Date: Sat, 26 Oct 2013 10:13:29 +0200 [thread overview]
Message-ID: <201310261013.29571.redlizard@gentoo.org> (raw)
In-Reply-To: <20131026074128.GB66946@gentoo.org>
On Saturday 26 October 2013 09:41:28 Fabian Groffen wrote:
> As you may or may not know, the prefix USE-flag is a hack that works in
> Portage, but violates specifications, because it is never defined in
> ebuilds that need it. Discussions here go back to not wanting to show
> elibc_XXX, kernel_XXX in IUSE (because user can't influence them) and
> prefix likewise. We should still solve this problem. While we're at
> it, I'd like to tackle bug #473598 [1] at the same time.
Not so! Any USE flags that are globally masked or forced are in the
implicit-iuse list. Or is that what you meant as the hack? I think it's
specified somewhere.
> Anyway, I was thinking more along the lines of using USE_EXPAND.
> There's also a USE_EXPAND_HIDDEN, and something like this [2] looks
> good.
USE_EXPAND is fine too, it's just a special case of a USE flag, after all. It
is perhaps more elegant than plain USE flags, and my plan was based on
kernel_* and friends anyway.
> In other words, I could think of having EPREFIX="$classic" or
> EPREFIX_TARGET="$rap", which could default to $classic in
> base/make.defaults.
It should default to "" in base/make.defaults. Only the prefix profiles should
set it to anything nonempty.
-- Ruud
next prev parent reply other threads:[~2013-10-26 8:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 22:54 [gentoo-alt] Names of Prefix variants Ruud Koolen
2013-10-26 0:23 ` Greg Turner
2013-10-26 0:28 ` Ruud Koolen
2013-10-26 7:41 ` Fabian Groffen
2013-10-26 8:13 ` Ruud Koolen [this message]
2013-10-26 9:28 ` Fabian Groffen
2013-10-31 15:50 ` heroxbd
2013-10-29 7:40 ` Michael Haubenwallner
2013-10-29 22:02 ` Ruud Koolen
2013-10-31 5:03 ` Jeremy Olexa
2013-10-31 7:37 ` Michael Haubenwallner
2013-11-18 4:28 ` Ruud Koolen
2013-11-18 9:24 ` Fabian Groffen
2013-11-18 15:33 ` Ruud Koolen
2013-11-19 10:20 ` heroxbd
2013-11-19 11:37 ` Michael Haubenwallner
2013-11-19 15:48 ` Fabian Groffen
2013-11-19 10:13 ` heroxbd
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=201310261013.29571.redlizard@gentoo.org \
--to=redlizard@gentoo.org \
--cc=gentoo-alt@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