1 |
On 04/11/2012 11:02 AM, David Leverton wrote: |
2 |
> Zac Medico wrote: |
3 |
>> Since the EAPI parsing behavior is optional for older EAPIs, package |
4 |
>> managers can simply trigger a warning when they detect non-conformant |
5 |
>> ebuilds in the wild, and eventually make it fatal after the community |
6 |
>> has had sufficient warning. |
7 |
> |
8 |
> Just to be clear, do you mean "if the PM doesn't detect an EAPI |
9 |
> assignment during parsing but the EAPI is non-0 after generating the |
10 |
> metadata, warn"? ยน Or something else? |
11 |
> |
12 |
> [1] As opposed to the already-decided "if the PM detects an EAPI line |
13 |
> during parsing but the EAPI is something else after generating the |
14 |
> metadata, fail" rule. |
15 |
|
16 |
The spec says "The package manager may optionally determine the \t{EAPI} |
17 |
of an ebuild by parsing it", which implies that you can implement a |
18 |
"pretend" mode that doesn't really determine the EAPI by parsing it, but |
19 |
parses it anyway and uses the result to generate deprecation warnings. A |
20 |
"pretend" mode like this is useful for initial deployment, in order to |
21 |
warn people with non-conformant ebuilds that are outside of the main tree. |
22 |
-- |
23 |
Thanks, |
24 |
Zac |