aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGöktürk Yüksek <gokturk@gentoo.org>2017-04-27 19:07:35 -0400
committerGöktürk Yüksek <gokturk@gentoo.org>2017-05-06 18:46:40 -0400
commite2d15f91cfb5fc3d7773ee70dc8675b78e6500ca (patch)
tree795b31ce6f5bf8a00bde3f4667bcac429c010e89
parentebuild-writing/misc-files/metadata: repoman does not depend on libxml2 anymore (diff)
downloaddevmanual-e2d15f91.tar.gz
devmanual-e2d15f91.tar.bz2
devmanual-e2d15f91.zip
ebuild-writing/error-handling: improve ebuild and eclass failure behavior
Instead of explaining the EAPI<=4 die behavior initially, explain the default behavior for the later EAPIs first. Remove the portage-specific bits from the paragraph. Reported-By: Benda Xu <heroxbd@gentoo.org>
-rw-r--r--ebuild-writing/error-handling/text.xml9
1 files changed, 4 insertions, 5 deletions
diff --git a/ebuild-writing/error-handling/text.xml b/ebuild-writing/error-handling/text.xml
index 40b8b5b..da9e88d 100644
--- a/ebuild-writing/error-handling/text.xml
+++ b/ebuild-writing/error-handling/text.xml
@@ -47,11 +47,10 @@ function can die in multiple places.
</p>
<p>
-Some portage-provided functions will automatically die upon failure. Others will
-not. It is for example safe to omit the <c>|| die</c> after a call to <c>epatch</c>,
-but not <c>emake</c>. The reason is that external binaries are not able to call
-die that is a bash function. You can see what commands are external binaries
-with <c>ls /usr/lib*/portage/bin/ebuild-helpers</c>. In <uri link="::ebuild-writing/eapi/#eapi=4">EAPI>=4</uri> all ebuild-helpers automatically die upon failure.
+Ebuild helpers from EAPI 4 and onwards automatically die on
+failure. Some eclass-provided functions will automatically die upon
+failure, others will not. Developers should check the
+<uri link="::eclass-reference/">eclass reference</uri> when in doubt.
</p>
<p>