On Sun, 18 Oct 2015 19:06:33 +0100
Ciaran McCreesh <ciaran.mccre...@googlemail.com> wrote:
> On Sun, 18 Oct 2015 20:00:11 +0200
> Alexis Ballier <aball...@gentoo.org> wrote:
> > On Sun, 18 Oct 2015 13:44:30 +0100
> > Ciaran McCreesh <ciaran.mccre...@googlemail.com> wrote:
> > [...]
> > > > - why should I ever want eapi6 src_prepare instead of
> > > > base_src_prepare ?
> > >
> > > Well base.eclass is supposed to be being removed, and is allegedly
> > > banned for all new ebuilds...
> > >
> > > But the big gain for everyone is in replacing a weird, overly
> > > clever and highly fragile collection of weirdness that's designed
> > > to mostly accept any dodgy input, with one that just gets you to
> > > give it a sane input to begin with.
> > >
> >
> > removing features is certainly not a gain for me
> >
> > after all, the safest program is the one that does nothing
>
> It's a good thing we've left in all the useful features, then.
>
A strict subset of it, indeed; what I was trying to understand is what
is the usefulness of eapply vs epatch or simply using 'epatch
"${PATCHES[@]}"' when proper patches do not fit in what you call 'all
the useful features': I haven't seen any, so that I know where to stand
on using that feature or not. It is simply inferior and deemed
unfixable until next EAPI.
