| 1 |
On 09.10.2012 23:19, Mike Frysinger wrote: |
| 2 |
> On Sunday 07 October 2012 13:58:04 justin wrote: |
| 3 |
>> On 10/7/12 7:36 PM, Jonathan Callen wrote: |
| 4 |
>>> You cannot check the value of IUSE in global scope in an eclass, as at |
| 5 |
>>> least portage actually unsets it before sourcing an eclass (also, it |
| 6 |
>>> is not defined in PMS what value IUSE would have at that point). |
| 7 |
>> |
| 8 |
>> Regarding your first point I copied the behavior from the |
| 9 |
>> toolchain.eclass and I thought it would work. Testing it, I see you are |
| 10 |
>> right. Any suggestion how to check for a USE being IUSE in an eclass? |
| 11 |
> |
| 12 |
> toolchain.eclass is testing its own IUSE which is why it works, not the IUSE |
| 13 |
> from ebuilds |
| 14 |
> -mike |
| 15 |
> |
| 16 |
|
| 17 |
Right I just saw this. |
| 18 |
Thanks, |
| 19 |
Justin |
Archives