summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUlrich Müller <ulm@gentoo.org>2015-10-21 18:47:05 +0200
committerUlrich Müller <ulm@gentoo.org>2015-11-08 20:29:19 +0100
commit01346659dfaf4057107dacc38bbeb7e7b0fc5e4f (patch)
tree7b0ce0dcb1d235a08bf912827214e3f4e1b1481b
parentEAPI 6: Bash version is 4.2. (diff)
downloadpms-01346659dfaf4057107dacc38bbeb7e7b0fc5e4f.tar.gz
pms-01346659dfaf4057107dacc38bbeb7e7b0fc5e4f.tar.bz2
pms-01346659dfaf4057107dacc38bbeb7e7b0fc5e4f.zip
Recommend setting the bash compatibility level.
-rw-r--r--ebuild-format.tex5
1 files changed, 4 insertions, 1 deletions
diff --git a/ebuild-format.tex b/ebuild-format.tex
index 61e3437..db6d7a1 100644
--- a/ebuild-format.tex
+++ b/ebuild-format.tex
@@ -3,7 +3,10 @@
\featurelabel{bash-version} The ebuild file format is in its basic form a subset of the format of
a bash script. The interpreter is assumed to be GNU bash, version as listed in
-table~\ref{tab:bash-version}, or any later version.
+table~\ref{tab:bash-version}, or any later version. If possible, the package manager should set
+the shell's compatibility level to the exact version specified. It must ensure that any such
+compatibility settings (e.g. the \t{BASH\_COMPAT} variable) are not exported to external programs.
+
The file encoding must be UTF-8 with Unix-style newlines. When sourced, the ebuild must define
certain variables and functions (see sections~\ref{sec:ebuild-vars} and~\ref{sec:ebuild-functions}
for specific information), and must not call any external programs, write anything to standard