1 |
>>>>> On Wed, 25 Feb 2015, hasufell wrote: |
2 |
|
3 |
>>> +As an example: if you use <c>epatch</c> in your ebuild, you <b>must</b> |
4 |
>>> +inherit <c>eutils.eclass</c> directly, even if another eclass (like distutils-r1) |
5 |
>>> +already inherits it. Exceptions to this policy must be discussed and documented. |
6 |
>>> +</warning> |
7 |
>> |
8 |
>> Documented, maybe. But I don't want to discuss a feature of my |
9 |
>> eclasses which is in place since more than a decade and works |
10 |
>> flawlessly. |
11 |
|
12 |
> What wording do you suggest instead? |
13 |
> Maybe "Exceptions to this policy are documented in the respective eclasses"? |
14 |
|
15 |
"Exceptions to this policy must be documented in the inheriting eclass." |
16 |
|
17 |
BTW, for new eclasses there should be a discussion in -dev anyway. |
18 |
|
19 |
Ulrich |