>>>>> On Wed, 25 Feb 2015, hasufell  wrote:

>>> +As an example: if you use <c>epatch</c> in your ebuild, you <b>must</b>
>>> +inherit <c>eutils.eclass</c> directly, even if another eclass (like 
>>> distutils-r1)
>>> +already inherits it. Exceptions to this policy must be discussed and 
>>> documented.
>>> +</warning>
>> 
>> Documented, maybe. But I don't want to discuss a feature of my
>> eclasses which is in place since more than a decade and works
>> flawlessly.

> What wording do you suggest instead?
> Maybe "Exceptions to this policy are documented in the respective eclasses"?

"Exceptions to this policy must be documented in the inheriting eclass."

BTW, for new eclasses there should be a discussion in -dev anyway.

Ulrich

Attachment: pgpxODKDKKzUx.pgp
Description: PGP signature

Reply via email to