1 |
On Mon, Mar 12, 2012 at 1:46 PM, Zac Medico <zmedico@g.o> wrote: |
2 |
> If we want to handle every possible screwup, including stray EAPI |
3 |
> assignments inside inherited eclasses, we still need to compare the |
4 |
> probed value to the value that's obtained from bash. |
5 |
|
6 |
Well, I wasn't intending to suggest that the repoman check need be the |
7 |
only one. However, preventing problems is at least as useful as |
8 |
detecting them. |
9 |
|
10 |
That said, it would probably best to have exactly one way to determine |
11 |
the official EAPI. If that is to parse the filename, then parse the |
12 |
filename. If it is to grep for a regexp and expect exactly one hit |
13 |
and parse it in a certain way, then do that. |
14 |
|
15 |
It might be that the "one" official way is to grep for a regexp and if |
16 |
you find it, use it, otherwise assume 0, 1, 2, 3, or 4 and source the |
17 |
ebuild for it. That still gives you only a single answer (well, |
18 |
except in situations where the current way is already broken). |
19 |
|
20 |
If people want to abuse the EAPI syntax I suppose we can generate an |
21 |
error, but ignoring it might be just as valid behavior. I'm not sure |
22 |
what happens if you define PN/etc in ebuild besides things breaking in |
23 |
a horrible manner. I'd put changing EAPI in the same category. |
24 |
|
25 |
Rich |