From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] base.eclass
Date: Sun, 08 Jul 2012 23:31:13 +0200 [thread overview]
Message-ID: <1341783073.8828.9.camel@belkin4> (raw)
In-Reply-To: <4FF9F499.4070704@necoro.eu>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
El dom, 08-07-2012 a las 22:59 +0200, René Neumann escribió:
> Am 08.07.2012 22:10, schrieb Michał Górny:
> > On Sun, 08 Jul 2012 19:49:25 +0200
> > René Neumann <lists@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].
> >
>
> Thanks for the clarification. As Mike already mentioned, one should
> probably change the ebuild description to reflect just that fact.
> (Because at the moment it just says the complete opposite.)
>
> - René
>
And, if we are supposed to stop using it, it should print some kind of
warning to remember developers to drop its usage
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-08 21:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 17:49 [gentoo-dev] base.eclass René Neumann
2012-07-08 17:54 ` Ciaran McCreesh
2012-07-08 18:02 ` Mike Gilbert
2012-07-08 20:10 ` Michał Górny
2012-07-08 20:59 ` René Neumann
2012-07-08 21:31 ` Pacho Ramos [this message]
2012-07-08 21:35 ` Alexis Ballier
2012-07-09 6:39 ` Michał Górny
2012-07-09 12:09 ` Alexis Ballier
2012-07-08 21:40 ` Andreas K. Huettel
2012-07-09 6:45 ` Michał Górny
2012-07-09 13:16 ` hasufell
2012-07-09 7:02 ` Ciaran McCreesh
2012-07-09 8:21 ` Samuli Suominen
2012-07-09 8:35 ` Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1341783073.8828.9.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox