Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Mike Frysinger <vapier@g.o>
Subject: Re: Fixing eclass code relying on ${IUSE} greps?
Date: Wed, 14 Sep 2011 15:20:51 -0400
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


References:
Fixing eclass code relying on ${IUSE} greps?
-- Michał Górny
Re: Fixing eclass code relying on ${IUSE} greps?
-- Mike Frysinger
Re: Fixing eclass code relying on ${IUSE} greps?
-- Michał Górny
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Fixing eclass code relying on ${IUSE} greps?
Next by thread:
[PATCH autotools-utils] Fail if myeconfargs is not an array.
Previous by date:
Re: new `usex` helper
Next by date:
Re: new `usex` helper


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.