Lines 11-16
compatibility settings (e.\,g.\ the \t{BASH_COMPAT} variable) are not exported t
Link Here
|
11 |
option of bash is set in the global scope of ebuilds. If set, failed pattern matches during |
11 |
option of bash is set in the global scope of ebuilds. If set, failed pattern matches during |
12 |
filename expansion result in an error when the ebuild is being sourced. |
12 |
filename expansion result in an error when the ebuild is being sourced. |
13 |
|
13 |
|
|
|
14 |
Name reference variables (introduced in Bash version~4.3) must not be used, except in local scope. |
15 |
|
14 |
The file encoding must be UTF-8 with Unix-style newlines. When sourced, the ebuild must define |
16 |
The file encoding must be UTF-8 with Unix-style newlines. When sourced, the ebuild must define |
15 |
certain variables and functions (see chapters~\ref{ch:ebuild-vars} and~\ref{ch:ebuild-functions} |
17 |
certain variables and functions (see chapters~\ref{ch:ebuild-vars} and~\ref{ch:ebuild-functions} |
16 |
for specific information), and must not call any external programs, write anything to standard |
18 |
for specific information), and must not call any external programs, write anything to standard |
17 |
- |
|
|