On Fri, 15 May 2009 20:12:03 +0100
Steven J Long <slong@rathaus.eclipse.co.uk> wrote:
> Robert R. Russell wrote:
> <snip>
> > If I understand the problem GLEP 55 is trying to solve correctly,
> > it stems from portage's assumption that an unknown EAPI is equal to
> > EAPI 0.
> 
> No, portage will reject an ebuild with an unknown EAPI, as per the
> spec.

You're confusing the term 'unknown' here.

Before an ebuild has had its metadata generated, its EAPI is unknown. At
this point, the package manager assumes EAPI 0.

After an ebuild has had its metadata generated, its EAPI is either
known or unsupported, but if known may be unspecified. If it is known
but unspecified, the package manager treats it as equivalent to EAPI 0.

Conceptually, these aren't the same thing.

-- 
Ciaran McCreesh