On Mittwoch, 12. Dezember 2007, Ciaran McCreesh wrote: > On Wed, 12 Dec 2007 23:14:24 +0100 > 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.
It's not perfect, but
<eclass>_pkg_setup() {
something_wrong && die
}
should work reasonably well.
> It's in PMS. svn co http://svn.repogirl.net/pms for a copy.
Right. But when you think every dev will read the PMS to find out what's fine
to do and what not for N++ EAPIs again and again, while he wants only a short
list of do's and don'ts, your bathing temperature is far above average.
What I do think - and no, I won't read this rediculous large
category/ebuild-x.y-rN-my.local.version-too-much-coffein-drinks.ebuild-epaiN-anyone-else-with-a-stupid-idea
thread - is, that EPAI changes and there implications apparently have not
been well thought out and the best we can do is to ensure there are as few
eclass/ebuild-relating differing EAPIs as possible.
Carsten
signature.asc
Description: This is a digitally signed message part.
