On Sat, 16 May 2009 11:27:10 +0200 Tobias Klausmann <[email protected]> wrote: > Change the spec, then.
If we change the spec, we can't do anything with the change until we're absolutely sure that everyone's updated both their ebuilds and their package manager for it. > Actually, I personally would prefer taking it out of the > parsed-by-bash part entirely. Add it as a shebang-like line at > the top: > > #EAPI-1 > > as the first or second line. Allowing it on the second line > allows you to later bolt on a true shebang-line if you should so > desire. Only having to look at the first two lines makes finding > it out easier (note that I don't call that parsing on purpose). Would mean we'd have to change every existing ebuild everywhere. > I was under the impression that it's illegal to change/set the > EAPI after using inherit. Nope. It's considered by some to be a QA violation, but EAPI's rules are the same as the rules for any other metadata variable. -- Ciaran McCreesh
signature.asc
Description: PGP signature
