1 |
On 13 March 2012 17:31, Brian Harring <ferringb@×××××.com> wrote: |
2 |
> Worse, it actually makes parsing _worse_ than it already is. What G55 |
3 |
> had going for it was ease of filtering out unsupported eapi's. |
4 |
> Literally just filter the readdir results. This behemoth Zac is |
5 |
> proposing basically requires throwing regex at it, and *is* able to |
6 |
> be tripped up since eapi's aren't strictly integers (1-prefix, |
7 |
> 4-python, 4-eapi3 if I wanted to intentionally be a dick and break |
8 |
> likely non-greedy implementations of the regex). |
9 |
|
10 |
Eh? How? If you make "." a forbidden character in an eapi |
11 |
specificiation, and make "." the delimiter |
12 |
|
13 |
dev-foo/foo-bar-2.3.4.eapi5.eb |
14 |
|
15 |
^^^^ |
16 |
|
17 |
How does that require regex? |
18 |
|
19 |
remove the .eb , and the last token remaining is the eapi . |
20 |
|
21 |
it doesn't clash with the existing system for 2 reasons, 1) the .eb |
22 |
extension and 2) "eapi5" is not a valid version token |
23 |
|
24 |
> Same angle, embedding it into the version space means that there can |
25 |
> be conflicts w/ PN. |
26 |
|
27 |
I'm confused as to how, can you give one theoretical example? |
28 |
|
29 |
dev-foo/foo-bar-2.3.4.eapi5.eb <-- eapi5 can't be a package name |
30 |
here, because its got the .eb suffix which means an EAPI *MUST* be |
31 |
specified |
32 |
|
33 |
and eapi5 also can't be a package name there, because then you're |
34 |
telling be it tokenizes as: |
35 |
|
36 |
category=dev-foo |
37 |
package=foo-bar-2.3.4.eapi5 |
38 |
version = undefined |
39 |
eapi = undefined |
40 |
|
41 |
Which is clearly illegal. |
42 |
|
43 |
> Basically... embedding it into the versioning like that, besides being |
44 |
> ugly as all hell, discards the main benefit g55 had- clear |
45 |
> identification of EAPI. |
46 |
|
47 |
It still seems "clear" to me. |
48 |
|
49 |
-- |
50 |
Kent |
51 |
|
52 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
53 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |