Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Wed, Sep 14, 2011 at 02:16:41PM -0500, Donnie Berkholz wrote:
> On 19:14 Tue 13 Sep , Brian Harring wrote:
> > 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.
>
> Why are people cloning anything if it's in eutils.eclass in gentoo-x86?
There are more repositories than just gentoo-x86, and overlay is *not*
the only configuration in use.
In the old days of the PM only handling a single overlay stack, what
you're suggesting would be less heinous- heinous in detail, but
pragmatic in reality. These days it's a regressive approach-
requiring everyone to slave gentoo-x86 isn't sane, nor is avoiding
eapi (resulting in people having to duplicate code into each
repository stack).
~harring
|
|
