[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/error-handling/

[Göktürk Yüksek]

commit:     e2d15f91cfb5fc3d7773ee70dc8675b78e6500ca
Author:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 27 23:07:35 2017 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Sat May  6 22:46:40 2017 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e2d15f91

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 <AT> gentoo.org>

 ebuild-writing/error-handling/text.xml | 9 ++++-----
 1 file 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>