On Fri, Aug 26, 2005 at 03:02:13PM -0700, Drake Wyrm wrote: > Brian Harring wrote: > > B) EAPI is pretty much bash env template switching > [snip] > > Perhaps the EAPI handling could be implemented using eclasses, rather > than something in the deep, dark, python-based internals. Effectively the implementation is essentially an eclass, but won't wind up in $PORTDIR/eclass due to the fact it's also slightly bound to python side. For example, the ebuild build operation class knows not to command the ebuild processor to execute the configure phase for eapi0, 'coz that hook doesn't exist. For >eap0, it commands it. That's about the extent of python side awareness at this point, beyond checking min/max eapi support. ~harring