1 |
On Sat, Dec 22, 2007 at 06:01:04PM +0800, Zhang Le wrote: |
2 |
> > |
3 |
> > Your algorithm: |
4 |
> > |
5 |
> > Does not work for existing ebuilds that have implicit EAPI 0. |
6 |
> |
7 |
> That's obvious. If no suffix, just treat it as EAPI 0. |
8 |
> I thought I don't need to say this explicitly. |
9 |
|
10 |
'# Copyright 1999-2007 Gentoo Foundation' |
11 |
|
12 |
Is that an EAPI? of course it is not, are you going to hardcode every |
13 |
possible ebuild header in your stupid _hack_ ? |
14 |
|
15 |
> > |
16 |
> > Does not work for existing ebuilds that have explicit EAPI. |
17 |
> |
18 |
> Even better, since we don't need suffix in the first place. Just define it in |
19 |
> ebuild. |
20 |
|
21 |
What? |
22 |
|
23 |
> > |
24 |
> > Does not work for future ebuilds. |
25 |
> |
26 |
> If defined in file does not work, then define in file name doesn't either. |
27 |
> They are interchangeable. |
28 |
|
29 |
No, they are not. |
30 |
|
31 |
> All could be get before sourcing. |
32 |
> I know you'd say people will use all syntaxes to define. But how many are |
33 |
> there? EAPI=1, EAPI="1" these are the two ways currently used in tree. |
34 |
> A simple qgrep can show that. |
35 |
> Two steps can guarantee you get the value |
36 |
> 1. strip " |
37 |
> 2. get the value |
38 |
|
39 |
And then you are stuck FOREVER into defining EAPI as a variable. |
40 |
|
41 |
You clearly haven't read anything on this thread. I suggest you go and |
42 |
do so before making a fool of yourself again. Please. |
43 |
|
44 |
Please guys, keep in mind that the fact that some of you understand what |
45 |
a filename is and are able to provide simple commands that extract a |
46 |
particular line from a file does not entitle you with the knowdledge |
47 |
required to contribute something useful to this discussion. |
48 |
|
49 |
- ferdy |
50 |
|
51 |
-- |
52 |
Fernando J. Pereda Garcimartín |
53 |
20BB BDC3 761A 4781 E6ED ED0B 0A48 5B0C 60BD 28D4 |