1 |
Zac Medico wrote: |
2 |
> Since the EAPI parsing behavior is optional for older EAPIs, package |
3 |
> managers can simply trigger a warning when they detect non-conformant |
4 |
> ebuilds in the wild, and eventually make it fatal after the community |
5 |
> has had sufficient warning. |
6 |
|
7 |
Just to be clear, do you mean "if the PM doesn't detect an EAPI |
8 |
assignment during parsing but the EAPI is non-0 after generating the |
9 |
metadata, warn"? ¹ Or something else? |
10 |
|
11 |
[1] As opposed to the already-decided "if the PM detects an EAPI line |
12 |
during parsing but the EAPI is something else after generating the |
13 |
metadata, fail" rule. |