1 |
On Thu, 8 Mar 2012 20:04:55 +0100 |
2 |
Ulrich Mueller <ulm@g.o> wrote: |
3 |
> > Err... so what happens if 'new parsing' detects EAPI 4 and 'old |
4 |
> > parsing' detects EAPI 5? |
5 |
> |
6 |
> This cannot happen for a legal ebuild: |
7 |
> - If the ebuild is EAPI 4, then sourcing it ("old parsing") must |
8 |
> detect EAPI 4. |
9 |
|
10 |
the problem here may be when "old parsing" will wrongly parse a |
11 |
malformed EAPI 42 assignment (so that new parsing doesnt detect an |
12 |
EAPI and assumes its 0) as EAPI 4. |
13 |
this is a purely hypothetical scenario that will be easily detected if |
14 |
it ever happens, though :) |
15 |
|
16 |
anyway, "new parsing" != "old parsing" should trigger a repoman |
17 |
warning for old EAPIs. |
18 |
|
19 |
A. |