--- 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/using-eclasses/text.xml @@ -26,7 +26,15 @@ link="::general-concepts/portage-cache"/>). </p> <p> -After inheriting an eclass, its provided functions can be used as normal. Here'san example ebuild, <c>foomatic-0.1-r2.ebuild</c>, which uses four eclasses: +After inheriting an eclass, its provided functions can be used as normal. +</p> +<warning> +You must not rely on provided functions of implicitly inherited eclasses. +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> +<p>Here'san example ebuild, <c>foomatic-0.1-r2.ebuild</c>, which uses four eclasses: </p> <codesample lang="ebuild"> -- 2.2.1
