| 1 |
--- |
| 2 |
ebuild-writing/using-eclasses/text.xml | 10 +++++++++- |
| 3 |
1 file changed, 9 insertions(+), 1 deletion(-) |
| 4 |
|
| 5 |
diff --git a/ebuild-writing/using-eclasses/text.xml b/ebuild-writing/using-eclasses/text.xml |
| 6 |
index de9ec7f..49ec23b 100644 |
| 7 |
--- a/ebuild-writing/using-eclasses/text.xml |
| 8 |
+++ b/ebuild-writing/using-eclasses/text.xml |
| 9 |
@@ -26,7 +26,15 @@ link="::general-concepts/portage-cache"/>). |
| 10 |
</p> |
| 11 |
|
| 12 |
<p> |
| 13 |
-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: |
| 14 |
+After inheriting an eclass, its provided functions can be used as normal. |
| 15 |
+</p> |
| 16 |
+<warning> |
| 17 |
+You must not rely on provided functions of implicitly inherited eclasses. |
| 18 |
+As an example: if you use <c>epatch</c> in your ebuild, you <b>must</b> |
| 19 |
+inherit <c>eutils.eclass</c> directly, even if another eclass (like distutils-r1) |
| 20 |
+already inherits it. Exceptions to this policy must be discussed and documented. |
| 21 |
+</warning> |
| 22 |
+<p>Here'san example ebuild, <c>foomatic-0.1-r2.ebuild</c>, which uses four eclasses: |
| 23 |
</p> |
| 24 |
|
| 25 |
<codesample lang="ebuild"> |
| 26 |
-- |
| 27 |
2.2.1 |
Archives