1 |
On Tue, 13 Sep 2011 12:21:31 +0200 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
> Such checks are used at least in autotools-utils & kde* eclasses, and |
4 |
> are done wrong there. Thus, I've created a little reusable snippet |
5 |
> suitable for eutils. |
6 |
|
7 |
Are you sure this is defined behaviour? IUSE is a fancy merged variable |
8 |
for eclasses, and I don't think we guarantee that the value visible to |
9 |
the ebuild at any particular point is the generated value used by the |
10 |
package mangler. In particular, what happens if you do something like |
11 |
this in an eclass: |
12 |
|
13 |
IUSE="foo" |
14 |
has_iuse bar && DEPEND="cat/bar" |
15 |
|
16 |
and then inherit from an ebuild that sets IUSE="bar", possibly after |
17 |
the inherit? What about if the bar comes from another eclass? |
18 |
|
19 |
Or worse... |
20 |
|
21 |
has_iuse bar && IUSE="bar" |
22 |
|
23 |
Now what? |
24 |
|
25 |
-- |
26 |
Ciaran McCreesh |