1 |
>>>>> On Wed, 25 Feb 2015, Julian Ospald wrote: |
2 |
|
3 |
> +<warning> |
4 |
> +You must not rely on provided functions of implicitly inherited eclasses. |
5 |
|
6 |
Not sure if this can be stated as a general policy. For example, if |
7 |
your ebuild inherits elisp.eclass then it is pointless to inherit also |
8 |
elisp-common.eclass, because it is guaranteed (and documented) that |
9 |
all the functions of the latter will also be available when inheriting |
10 |
the former. |
11 |
|
12 |
> +As an example: if you use <c>epatch</c> in your ebuild, you <b>must</b> |
13 |
> +inherit <c>eutils.eclass</c> directly, even if another eclass (like distutils-r1) |
14 |
> +already inherits it. Exceptions to this policy must be discussed and documented. |
15 |
> +</warning> |
16 |
|
17 |
Documented, maybe. But I don't want to discuss a feature of my |
18 |
eclasses which is in place since more than a decade and works |
19 |
flawlessly. |
20 |
|
21 |
Ulrich |