| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Wed, 25 Feb 2009 04:04:46 +0100 |
| 3 |
> Luca Barbato <lu_zero@g.o> wrote: |
| 4 |
>> given that the simplest thing is hacking ebuild.sh and extract eapi |
| 5 |
>> with a simple C program (you can use pcre or ragel if you want) |
| 6 |
>> exactly before the ebuild source: |
| 7 |
> |
| 8 |
> That you're bringing ebuild.sh into this shows you still haven't worked |
| 9 |
> out how the process works. There is no need to use ebuild.sh (which is |
| 10 |
> a very good thing, because launching bash is slooooooooooooow) when |
| 11 |
> there's valid metadata. |
| 12 |
|
| 13 |
it there is a valid metadata you have everything there already and you |
| 14 |
don't have to parse the ebuild so... |
| 15 |
|
| 16 |
>>> So you have patches for Portage? Please show them. |
| 17 |
>> Up there what's enough to check the viability for the solution. |
| 18 |
> |
| 19 |
> No, it's completely wrong. ebuild.sh has nothing to do with this. |
| 20 |
|
| 21 |
Is there another place in portage that extracts the EAPI value? |
| 22 |
|
| 23 |
> Yes, it will warn noisily. This is unacceptable, since stable users |
| 24 |
> will have months and months of noise when new rules come along. |
| 25 |
|
| 26 |
"unacceptable"... |
| 27 |
|
| 28 |
as in "it's ugly to see"... |
| 29 |
|
| 30 |
|
| 31 |
lu |
| 32 |
|
| 33 |
-- |
| 34 |
|
| 35 |
Luca Barbato |
| 36 |
Gentoo Council Member |
| 37 |
Gentoo/linux Gentoo/PPC |
| 38 |
http://dev.gentoo.org/~lu_zero |
Archives