| 1 |
El jue, 20-09-2012 a las 02:14 -0400, Alexandre Rostovtsev escribió: |
| 2 |
> Revised to use a separate variable for the name of the flag instead of |
| 3 |
> reading IUSE, as suggested by Ciaran McCreesh. As a result of this |
| 4 |
> change, vala.eclass now defaults to assuming that vala support is |
| 5 |
> optional (which is the case in an overwhelming majority of ebuilds that |
| 6 |
> would want to use this eclass). |
| 7 |
|
| 8 |
Sorry but, why even in_iuse function from eutils.eclass cannot be used? |
| 9 |
If that is really not allowed, why we have that function in |
| 10 |
eutils.eclass? |
| 11 |
|
| 12 |
There are lots of cases in eclasses relying on things like original |
| 13 |
suggested way or in_iuse from eutils.eclass and would like to clarify |
| 14 |
things before going with a more complex way than original. |
| 15 |
|
| 16 |
I already know Ciaran's opinion on this, but would like to know more |
| 17 |
opinion and, most important, is this is really allowed or not and, if |
| 18 |
not, we should try to migrate current eclasses to the "fixed" way if |
| 19 |
there is really a way providing similar function. |
Archives