| 1 |
Hi, |
| 2 |
|
| 3 |
> When EAPI 2 goes live built_with_use should probably die for most |
| 4 |
> cases. |
| 5 |
|
| 6 |
I don't understand here: you mean die like being removed or die like |
| 7 |
the die call in an ebuild? If I understood correctly the following it |
| 8 |
should be the latter. |
| 9 |
|
| 10 |
> Are there valid use cases for built_with_use that are not |
| 11 |
> covered by the use deps in EAPI 2? |
| 12 |
|
| 13 |
I can think of checks like: |
| 14 |
- foo is a dep/rdep of bar |
| 15 |
- foo has a "plugin like" architecture |
| 16 |
- bar will "work" with minimal foo |
| 17 |
- most people will expect some features in bar that come with foo's |
| 18 |
plugins |
| 19 |
- we might want to display warnings for the most useful features |
| 20 |
- having useflags in bar for each of foo's useflags doesn't seem wise |
| 21 |
|
| 22 |
|
| 23 |
Ok that's not really a nice example but I can't think of anything |
| 24 |
better at the moment. |
| 25 |
|
| 26 |
By the way, how will the --missing option of built_with_use be handled |
| 27 |
by eapi 2? |
| 28 |
|
| 29 |
Alexis. |
Archives