1 |
On 05/21/2016 12:15 AM, Michał Górny wrote: |
2 |
> Ensure that all USE_EXPAND variables are always exported with filtered |
3 |
> USE flags inside, even if none of those flags are declared in IUSE. |
4 |
> This is the behavior required for EAPI 5+ by the PMS. |
5 |
> |
6 |
> Since the behavior for earlier EAPIs is left undefined and having |
7 |
> different behavior would be confusing to users, apply it in earlier |
8 |
> EAPIs as well. |
9 |
|
10 |
The patch looks correct. However, I think it's arguable that the |
11 |
existing portage behavior makes more sense that what PMS dictates, |
12 |
because why should USE_EXPAND have any effect on a package which doesn't |
13 |
declare the corresponding flags in IUSE? |
14 |
|
15 |
Anyway, given the invasive nature of the proposed change, it's probably |
16 |
a good idea to have the council weigh in on this. |
17 |
-- |
18 |
Thanks, |
19 |
Zac |