1 |
On Wed, Sep 14, 2011 at 15:16, Michał Górny wrote: |
2 |
> On Wed, 14 Sep 2011 15:10:23 -0400 Mike Frysinger wrote: |
3 |
>> On Wed, Sep 14, 2011 at 06:38, Michał Górny wrote: |
4 |
>> > As the 'has_iuse' thread worked out, right now PMS doesn't allow us |
5 |
>> > to grep IUSE for random values during runtime. Thus, all eclasses |
6 |
>> > using that to enable features per ebuild-defined IUSE are broken. |
7 |
>> |
8 |
>> this statement isnt exactly clear. no, eclasses cannot leverage IUSE |
9 |
>> from ebuilds (and vice versa). but eclasses/ebuilds can leverage |
10 |
>> their own IUSE value. |
11 |
> |
12 |
> Erm, that's not really true. Consider that usually eclass functions are |
13 |
> called from ebuilds. At the time of calling, IUSE can basically contain |
14 |
> anything; if PM doesn't care much, that'd be probably last values set |
15 |
> -- ebuild values. |
16 |
|
17 |
i was referring to global scope. in src_* pkg_* funcs, the code |
18 |
should see the merged value. or maybe i havent read the spec close |
19 |
enough. |
20 |
-mike |