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