>>>>> On Fri, 6 Apr 2012, David Leverton wrote:

>> Right, assigning the same EAPI twice would be an example for an
>> ebuild that is invalid but accepted by the package manager. But
>> would this cause any problems?

> It's not that it's a problem in itself, it just struck me as an edge
> case with the potential for implementations to differ.  As long as
> everyone's clear what the rules are it's fine.

Maybe the spec should say that the first match must be used:

"The package manager may optionally determine the EAPI of an ebuild by
parsing it, using the first match for the above regular expression
within the above line number limit."

Ulrich