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.

> > 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.

> >> unknown isn't unsupported?
> > 
> > Huh? Please explain what you mean.
> 
> mv cat/pkg-version.ebuild cat/pkg-version_foo.ebuild
> 
> emerge -vp pkg
> 
> portage will warn about not knowing pkg-version_foo and will ignore
> it.

Yes, it will warn noisily. This is unacceptable, since stable users
will have months and months of noise when new rules come along.

-- 
Ciaran McCreesh