-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Freitag, 13. März 2015, 21:09:29 schrieb Jeroen Roovers:
> > From: Ian Delaney
> >
> > This single change will make my commits of last 2 years a violation
> > of policy, in a retrograde manner ofcourse.
>
> You'll have to fix those ebuilds. The
> From: Ian Delaney
> This single change will make my commits of last 2 years a violation
> of policy, in a retrograde manner ofcourse.
You'll have to fix those ebuilds. The policy was already in place
before[1] you were around[2].
> The flaw here is that it is using a black and white and red
implicit eclass inherits
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Begin forwarded message:
Date: Sat, 28 Feb 2015 10:43:52 +0800
From: Ian Delaney
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] Document policy of not relying on
implicit eclass
> On Wed, 25 Feb 2015, hasufell wrote:
>>> +As an example: if you use epatch in your ebuild, you must
>>> +inherit eutils.eclass directly, even if another eclass (like
>>> distutils-r1)
>>> +already inherits it. Exceptions to this policy must be discussed and
>>> documented.
>>> +
>>
>> Do
On 02/25/2015 05:55 PM, Ulrich Mueller wrote:
>> On Wed, 25 Feb 2015, Julian Ospald wrote:
>
>> +
>> +You must not rely on provided functions of implicitly inherited eclasses.
>
> Not sure if this can be stated as a general policy. For example, if
> your ebuild inherits elisp.eclass then it i
> On Wed, 25 Feb 2015, Julian Ospald wrote:
> +
> +You must not rely on provided functions of implicitly inherited eclasses.
Not sure if this can be stated as a general policy. For example, if
your ebuild inherits elisp.eclass then it is pointless to inherit also
elisp-common.eclass, because
---
ebuild-writing/using-eclasses/text.xml | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/ebuild-writing/using-eclasses/text.xml
b/ebuild-writing/using-eclasses/text.xml
index de9ec7f..49ec23b 100644
--- a/ebuild-writing/using-eclasses/text.xml
+++ b/ebuild-writing/
