List Archive: gentoo-dev
| Navigation: |
|
Lists:
gentoo-dev:
< Prev
By Thread
Next >
< Prev
By Date
Next >
|
| Headers: |
|
To:
|
gentoo-dev@g.o
|
|
From:
|
Luca Barbato <lu_zero@g.o>
|
|
Subject:
|
Re: Issues regarding glep-55 (Was: [gentoo-council] Re: Preliminary Meeting-Topics for 12 February 2009)
|
|
Date:
|
Wed, 25 Feb 2009 16:56:04 +0100
|
|
Ciaran McCreesh wrote:
> On Wed, 25 Feb 2009 04:04:46 +0100
> Luca Barbato <lu_zero@g.o> wrote:
>> given that the simplest thing is hacking ebuild.sh and extract eapi
>> with a simple C program (you can use pcre or ragel if you want)
>> exactly before the ebuild source:
>
> That you're bringing ebuild.sh into this shows you still haven't worked
> out how the process works. There is no need to use ebuild.sh (which is
> a very good thing, because launching bash is slooooooooooooow) when
> there's valid metadata.
it there is a valid metadata you have everything there already and you
don't have to parse the ebuild so...
>>> So you have patches for Portage? Please show them.
>> Up there what's enough to check the viability for the solution.
>
> No, it's completely wrong. ebuild.sh has nothing to do with this.
Is there another place in portage that extracts the EAPI value?
> Yes, it will warn noisily. This is unacceptable, since stable users
> will have months and months of noise when new rules come along.
"unacceptable"...
as in "it's ugly to see"...
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
|
|