On Thu, 20 Dec 2007 16:57:54 +0100 Michael Haubenwallner <[EMAIL PROTECTED]> wrote: > What if we do not start with "EAPI=1" variable, but "eapi 1" function > immediately ?
Uhhhhh. Then we're back to the zillion months wait before people can use anything. > *) Given it is the first bash-command in the ebuild: > Just 'echo' the required EAPI and exit while PM is in "look-for-eapi" > mode (remember 'eapi' function is part of PM, or profile.bashrc as > fallback for ancient PM). There isn't a look for eapi mode. > *) As 'eapi' being a bash function, it could *migrate* the > bash-environment from the PM's default EAPI to the given one - or just > spit "cannot migrate EAPI from A to B"... Uh... No it couldn't. And there's no default EAPI. > *) Or just spit a message "update your PM" (from profile.bashrc) ... Uh... No it couldn't. Please don't comment any further until you understand how this whole thing works. -- Ciaran McCreesh
signature.asc
Description: PGP signature
