On Wed, 12 Dec 2007 23:14:24 +0100 Carsten Lohrke <[EMAIL PROTECTED]> wrote: > I disagree here. It would be annoying and possibly even hindering in > future not being able to use higher EAPI features in eclasses. Point > is the eclass has to check, if the author of an ebuild sets another > EAPI and throw an error, in this case.
There is no way for an eclass to throw an error. Nor, with the current way Portage implements EAPI, is there a way to add such a way. > The most basic issue, which we didn't even discuss yet, afaik, is how > to make every developer aware which feature belongs to which EAPI. I > freely admit, I do not know that. Is there a list somewhere? It's in PMS. svn co http://svn.repogirl.net/pms for a copy. -- Ciaran McCreesh
signature.asc
Description: PGP signature
