| 1 |
Paul de Vrieze wrote: |
| 2 |
> On Tuesday 14 February 2006 13:44, Alec Warner wrote: |
| 3 |
> |
| 4 |
>>Well that problem would be, no one wants to modify everything in |
| 5 |
>>app-portage/ :). If my portage EAPI is 1, but my tools don't support |
| 6 |
>>processing +- in IUSE, how does EAPI help me here? The support check |
| 7 |
>>is only for portage_const, so the tool remains fucked. Unless I'm |
| 8 |
>>missing something. |
| 9 |
> |
| 10 |
> |
| 11 |
> Tools should also be EAPI aware. I know too many aren't, but that doesn't |
| 12 |
> mean they shouldn't be. |
| 13 |
> |
| 14 |
> Paul |
| 15 |
> |
| 16 |
|
| 17 |
I guess my point here is, last I checked we can't pass an EAPI less than |
| 18 |
portage_const.EAPI. |
| 19 |
|
| 20 |
In this example, say portage's EAPI is at 2, but my tool only handles |
| 21 |
EAPI 0, there is no way to set this in portage so I get EAPI 0 results. |
| 22 |
So perhaps we need this implemented as well. |
| 23 |
|
| 24 |
-Alec |
Archives