On Wed, 12 Dec 2007 09:22:41 -0500 Doug Klima <[EMAIL PROTECTED]> wrote: > My point is it's fine to state this, however there needs to be > enforcement of this in the associated utilities. repoman, etc. > Unfortunately, eclasses are not checked at all at commit time, which > would allow developers to make this potentially catastrophic change.
Well, the other option is to enforce it via the package manager. But that's enforcing tree policy via EAPI, which we were trying to avoid. > So we're going to have "eapi 1 && inherit foo-eapi1.eclass" allowable > in "foo.eclass"? When will this "eapi" keyword be available for > eclasses to use? [[ $EAPI == 1 ]] Adding an eapi keyword would require a new EAPI, so you'd have to do the variable test for 0 and 1 anyway (and note that the empty EAPI is exactly like EAPI 0, and you can't assume that you'll get one or the other). -- Ciaran McCreesh
signature.asc
Description: PGP signature
