| 1 |
For a long time (about a year, as far as I can tell) PMS has failed to |
| 2 |
document the bash version needed properly. Relying on PMS will not yield a |
| 3 |
working package manager in this case as in-tree ebuilds and eclasses have |
| 4 |
moved on for quite some time. This simple one-character fix should make PMS |
| 5 |
respect reality for that part again: |
| 6 |
|
| 7 |
|
| 8 |
diff --git a/ebuild-format.tex b/ebuild-format.tex |
| 9 |
index d6c8270..d814cfa 100644 |
| 10 |
--- a/ebuild-format.tex |
| 11 |
+++ b/ebuild-format.tex |
| 12 |
@@ -2,7 +2,7 @@ |
| 13 |
\label{sec:ebuild-format} |
| 14 |
|
| 15 |
The ebuild file format is in its basic form a subset of the format of a bash |
| 16 |
script. The interpreter |
| 17 |
-is assumed to be GNU bash, version 3.0 or later. The file encoding must be |
| 18 |
UTF-8 with Unix-style |
| 19 |
+is assumed to be GNU bash, version 3.2 or later. The file encoding must be |
| 20 |
UTF-8 with Unix-style |
| 21 |
newlines. When sourced, the |
| 22 |
ebuild must define certain variables and functions (see |
| 23 |
sections~\ref{sec:ebuild-vars} and |
| 24 |
\ref{sec:ebuild-functions} for specific information), and must not call any |
| 25 |
external programs, write |
Archives