| 1 |
On Wed, 14 Sep 2011 15:10:23 -0400 |
| 2 |
Mike Frysinger <vapier@g.o> wrote: |
| 3 |
|
| 4 |
> On Wed, Sep 14, 2011 at 06:38, Michał Górny wrote: |
| 5 |
> > As the 'has_iuse' thread worked out, right now PMS doesn't allow us |
| 6 |
> > to grep IUSE for random values during runtime. Thus, all eclasses |
| 7 |
> > using that to enable features per ebuild-defined IUSE are broken. |
| 8 |
> |
| 9 |
> this statement isnt exactly clear. no, eclasses cannot leverage IUSE |
| 10 |
> from ebuilds (and vice versa). but eclasses/ebuilds can leverage |
| 11 |
> their own IUSE value. |
| 12 |
|
| 13 |
Erm, that's not really true. Consider that usually eclass functions are |
| 14 |
called from ebuilds. At the time of calling, IUSE can basically contain |
| 15 |
anything; if PM doesn't care much, that'd be probably last values set |
| 16 |
-- ebuild values. |
| 17 |
|
| 18 |
Remember than calling a sourced function does not re-evaluate the |
| 19 |
eclass it was sourced from. |
| 20 |
|
| 21 |
-- |
| 22 |
Best regards, |
| 23 |
Michał Górny |
Archives