| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Mike Frysinger wrote: |
| 5 |
> On Sunday 04 November 2007, Andrew Gaffney wrote: |
| 6 |
>> Zac Medico wrote: |
| 7 |
>>> -----BEGIN PGP SIGNED MESSAGE----- |
| 8 |
>>> Hash: SHA1 |
| 9 |
>>> |
| 10 |
>>> Mike Frysinger wrote: |
| 11 |
>>>> userland_* and all other profile-expanded USE flags are "magical" and |
| 12 |
>>>> arent available for user consumption. that is how i view IUSE. it was |
| 13 |
>>>> my understanding that portage was going to get fixed to automatically |
| 14 |
>>>> include the profile-expanded ones and so adding anything to IUSE now for |
| 15 |
>>>> ebuilds is dumb when they're just going to get turned around and |
| 16 |
>>>> removed. the same goes for all implicit/automatic USE expanding things. |
| 17 |
>>>> portage can do this for us, so having developers track it themselves |
| 18 |
>>>> seems like a waste of time. -mike |
| 19 |
>>> Fair enough, but we need to define a way to "automatically include |
| 20 |
>>> the profile-expanded ones" since none currently exists. One thing |
| 21 |
>>> that I don't like about using USE_EXPAND_HIDDEN is that ARCH isn't a |
| 22 |
>>> USE_EXPAND. It would have been more consistent if it had been, |
| 23 |
>>> along with KERNEL, ELIBC, and USERLAND. |
| 24 |
>> Why not turn it into one? The whole USE="${ARCH}" thing is inconsistent |
| 25 |
>> with the USE_EXPANDed KERNEL, ELIBC, AND USERLAND. Yes, I know that it's |
| 26 |
>> been around a lot longer than the others, but that's not a good reason for |
| 27 |
>> keeping it the way it is. |
| 28 |
>> |
| 29 |
>> I don't think it would be a difficult transition. Is there any reason that |
| 30 |
>> portage can't set both USE=${ARCH} *and* USE=arch_${ARCH} for a while |
| 31 |
>> (until all ebuilds have been changed to use the new USE_EXPANDed form)? We |
| 32 |
>> could even just have portage set both forms indefinitely (the old form does |
| 33 |
>> no harm if nothing is using it). |
| 34 |
> |
| 35 |
> an interesting line of thinking and quite logical ... i dont see any arguments |
| 36 |
> against it other than "it's always been this way" and considering the |
| 37 |
> advantages for everyone, i dont think that offsets the pros |
| 38 |
> -mike |
| 39 |
|
| 40 |
For the USE=arch_${ARCH} part, we only have to add ARCH to |
| 41 |
USE_EXPAND in the base profile. For generating the implicit IUSE, we |
| 42 |
can introduce a new profile variable (rather than hardcode them). |
| 43 |
For example, we can define IUSE_EXPAND_IMPLICIT="ARCH ELIBC KERNEL |
| 44 |
USERLAND" and that will cause every package to inherit the |
| 45 |
corresponding USE_EXPAND flags in it's IUSE. |
| 46 |
|
| 47 |
Zac |
| 48 |
-----BEGIN PGP SIGNATURE----- |
| 49 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 50 |
|
| 51 |
iD8DBQFHLkrj/ejvha5XGaMRAmC4AJ9bnhm3lysB/2V+CtPqjmI9g61TYgCg54/K |
| 52 |
RFFucPFpdLUqnykuGKQz+3g= |
| 53 |
=pNDU |
| 54 |
-----END PGP SIGNATURE----- |
| 55 |
-- |
| 56 |
gentoo-portage-dev@g.o mailing list |
Archives