On Tue, Sep 13, 2011 at 09:02:28PM -0500, Donnie Berkholz wrote: > On 17:56 Tue 13 Sep , Mike Frysinger wrote: > > useful enough for EAPI ? or should i just stick it into eutils.eclass > > ? OR BOTH !? > > I prefer to avoid EAPI whenever possible, as it just makes things slower > and more complex.
Exactly the wrong approach; it winds up with master repositories/overlays cloning the functionality all over the damn place. Do both. Specifically, do it right- get it into the format (so it can be relied on and isn't adhoc BS that proceeded EAPI), then push a compat implementation into eclasses for usage by EAPI's less than 5. You get the feature now, and it's sorted properly for moving forward. Not that complex. And yes I'm tired of people bitching about compatibility. I recall a similar group of folk bitching about the lack of compatibility prior to EAPI... it's annoying. </rant> ~brian
