From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Let's populate IUSE_IMPLICIT in the base profile
Date: Thu, 27 Sep 2012 12:02:58 -0400 [thread overview]
Message-ID: <506478B2.10505@gentoo.org> (raw)
In-Reply-To: <CAJ0EP439KQLzdY0viCxSKNkhN=oCMfpJG80BuxDrvR=5PQYGOw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 27/09/12 11:57 AM, Mike Gilbert wrote:
> On Thu, Sep 13, 2012 at 1:40 AM, Zac Medico <zmedico@gentoo.org>
> wrote:
>> Hi,
>>
>> The council has approved [1] "Profile IUSE injection" [2] for
>> inclusion in EAPI 5, and in latest Portage we have experimental
>> EAPI 5_pre2 [3] which implements all of the approved features.
>> So, now would be a good time to start populating IUSE_IMPLICIT
>> with whatever values may be appropriate.
>>
>> What values belong there? Some of the flags that appear in
>> profiles/base/use.mask might make good candidates, such as prefix
>> and selinux. How about other special flags like bootstrap, build,
>> and test?
>>
>
> prefix and test make sense to me. I'm not so familiar with the
> others.
>
build is specifically for catalyst and/or for building the stages,
right? If so, this one makes sense to me to add.
bootstrap I would guess is similar? Unsure how that one is used at
present. If IUSE_IMPLICIT would still allow the boostrapping tool to
set the use flag, i see no issues having it in the list.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iF4EAREIAAYFAlBkeLIACgkQ2ugaI38ACPAh/QEAvfgmEDRGykF+3OvSRJVD684J
z60BrRXTWBYwi0ngmkABAIrolomS0leqwqpt7iX9RhYvctwId1CClZZ7P88+Ms6L
=R1e4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-09-27 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 5:40 [gentoo-dev] Let's populate IUSE_IMPLICIT in the base profile Zac Medico
2012-09-27 15:57 ` Mike Gilbert
2012-09-27 16:02 ` Ian Stakenvicius [this message]
2012-09-27 17:45 ` Ian Stakenvicius
2012-09-27 17:56 ` Zac Medico
2012-10-30 8:24 ` 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=506478B2.10505@gentoo.org \
--to=axs@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