On Mon, 9 Jul 2012 08:39:38 +0200
Michał Górny <mgo...@gentoo.org> wrote:
> On Sun, 8 Jul 2012 17:35:08 -0400
> Alexis Ballier <aball...@gentoo.org> wrote:
>
> > On Sun, 8 Jul 2012 22:10:02 +0200
> > Michał Górny <mgo...@gentoo.org> wrote:
> >
> > > On Sun, 08 Jul 2012 19:49:25 +0200
> > > René Neumann <li...@necoro.eu> wrote:
> > >
> > > > Hi all,
> > > >
> > > > I'd like just to receive a short clarification about the
> > > > 'status' of base.eclass: Is this eclass expected to be available
> > > > everywhere, i.e. should each eclass make sure it imports and
> > > > incorporates it. Or is it just an eclass like the others and
> > > > ebuilds should make sure they inherit it if needed?
> > >
> > > No. It is unmaintained, has serious design flaws and it simply
> > > should not be used anywhere. At least in EAPI != [01].
> > >
> >
> > what is the PATCHES=() replacement in new eapis? (mainly why i use
> > base.eclass more and more these days)
>
> That's what I used:
>
> [[ ${PATCHES} ]] && epatch "${PATCHES[@]}"
>
and ? thanks, I can read the code :)
are you suggesting people to duplicate the code ? this is in no way a
replacement...
A.
