| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 27/09/12 11:57 AM, Mike Gilbert wrote: |
| 5 |
> On Thu, Sep 13, 2012 at 1:40 AM, Zac Medico <zmedico@g.o> |
| 6 |
> wrote: |
| 7 |
>> Hi, |
| 8 |
>> |
| 9 |
>> The council has approved [1] "Profile IUSE injection" [2] for |
| 10 |
>> inclusion in EAPI 5, and in latest Portage we have experimental |
| 11 |
>> EAPI 5_pre2 [3] which implements all of the approved features. |
| 12 |
>> So, now would be a good time to start populating IUSE_IMPLICIT |
| 13 |
>> with whatever values may be appropriate. |
| 14 |
>> |
| 15 |
>> What values belong there? Some of the flags that appear in |
| 16 |
>> profiles/base/use.mask might make good candidates, such as prefix |
| 17 |
>> and selinux. How about other special flags like bootstrap, build, |
| 18 |
>> and test? |
| 19 |
>> |
| 20 |
> |
| 21 |
> prefix and test make sense to me. I'm not so familiar with the |
| 22 |
> others. |
| 23 |
> |
| 24 |
|
| 25 |
build is specifically for catalyst and/or for building the stages, |
| 26 |
right? If so, this one makes sense to me to add. |
| 27 |
|
| 28 |
bootstrap I would guess is similar? Unsure how that one is used at |
| 29 |
present. If IUSE_IMPLICIT would still allow the boostrapping tool to |
| 30 |
set the use flag, i see no issues having it in the list. |
| 31 |
|
| 32 |
|
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 35 |
|
| 36 |
iF4EAREIAAYFAlBkeLIACgkQ2ugaI38ACPAh/QEAvfgmEDRGykF+3OvSRJVD684J |
| 37 |
z60BrRXTWBYwi0ngmkABAIrolomS0leqwqpt7iX9RhYvctwId1CClZZ7P88+Ms6L |
| 38 |
=R1e4 |
| 39 |
-----END PGP SIGNATURE----- |
Archives