| 1 |
The wording's rather unclear on what 'nonfatal die' does. To avoid |
| 2 |
arguing whether calling die is a 'failure', explicitly say that nonfatal |
| 3 |
doesn't stop die or assert. |
| 4 |
--- |
| 5 |
pkg-mgr-commands.tex | 5 +++-- |
| 6 |
1 files changed, 3 insertions(+), 2 deletions(-) |
| 7 |
|
| 8 |
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex |
| 9 |
index 0278aec..b87bb49 100644 |
| 10 |
--- a/pkg-mgr-commands.tex |
| 11 |
+++ b/pkg-mgr-commands.tex |
| 12 |
@@ -16,8 +16,9 @@ The following commands affect this behaviour: |
| 13 |
\begin{description} |
| 14 |
\item[nonfatal] \featurelabel{nonfatal} Executes the remainder of its arguments as a command, |
| 15 |
preserving the exit status. If this results in a command being called that would normally abort |
| 16 |
- the build process due to a failure, instead a non-zero exit status shall be returned. Only in |
| 17 |
- EAPIs listed in table~\ref{tab:commands-die-table} as supporting \t{nonfatal}. |
| 18 |
+ the build process due to a failure (but not due to an explicit \t{die} or \{assert} call), |
| 19 |
+ instead a non-zero exit status shall be returned. Only in EAPIs listed in |
| 20 |
+ table~\ref{tab:commands-die-table} as supporting \t{nonfatal}. |
| 21 |
\end{description} |
| 22 |
|
| 23 |
\begin{centertable}{EAPI Command Failure Behaviour} \label{tab:commands-die-table} |
| 24 |
-- |
| 25 |
1.6.3.3 |
Archives