| 1 |
On Tue, 13 Sep 2011 11:32:40 +0100 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Tue, 13 Sep 2011 12:21:31 +0200 |
| 5 |
> Michał Górny <mgorny@g.o> wrote: |
| 6 |
> > Such checks are used at least in autotools-utils & kde* eclasses, |
| 7 |
> > and are done wrong there. Thus, I've created a little reusable |
| 8 |
> > snippet suitable for eutils. |
| 9 |
> |
| 10 |
> Are you sure this is defined behaviour? IUSE is a fancy merged |
| 11 |
> variable for eclasses, and I don't think we guarantee that the value |
| 12 |
> visible to the ebuild at any particular point is the generated value |
| 13 |
> used by the package mangler. |
| 14 |
|
| 15 |
True. I guess there's no way to tell whether a particular IUSE is |
| 16 |
defined in the ebuild then? Hrm, I guess we'll need to break API compat |
| 17 |
(and a number of ebuilds then) to get rid of this. |
| 18 |
|
| 19 |
-- |
| 20 |
Best regards, |
| 21 |
Michał Górny |
Archives