| 1 |
--- |
| 2 |
appendices.tex | 25 ++++++++++++++----------- |
| 3 |
1 file changed, 14 insertions(+), 11 deletions(-) |
| 4 |
|
| 5 |
diff --git a/appendices.tex b/appendices.tex |
| 6 |
index 8c97734..dd40041 100644 |
| 7 |
--- a/appendices.tex |
| 8 |
+++ b/appendices.tex |
| 9 |
@@ -26,12 +26,13 @@ been abused in the past. |
| 10 |
|
| 11 |
\chapter{Historical Curiosities} |
| 12 |
|
| 13 |
-The items described in this chapter are included for information only. Unless otherwise noted, |
| 14 |
-they were deprecated or abandoned long before \t{EAPI} was introduced. Ebuilds must not use these |
| 15 |
-features, and package managers should not be changed to support them. |
| 16 |
+\section{Long-obsolete Features} |
| 17 |
|
| 18 |
-\section{If-else USE Blocks} |
| 19 |
+The items described in this section are included for information only. Unless otherwise noted, they |
| 20 |
+were deprecated or abandoned long before EAPI was introduced. Ebuilds must not use these features, |
| 21 |
+and package managers should not be changed to support them. |
| 22 |
|
| 23 |
+\subsection{If-else USE blocks} |
| 24 |
Historically, Portage supported if-else use conditionals, as shown by |
| 25 |
listing~\ref{lst:if-else-use-listing}. The block before the colon would be taken if the condition |
| 26 |
was met, and the block after the colon would be taken if the condition was not met. |
| 27 |
@@ -49,27 +50,29 @@ DEPEND=" |
| 28 |
\end{verbatim} |
| 29 |
\end{listing} |
| 30 |
|
| 31 |
-\section{cvs Versions} |
| 32 |
- |
| 33 |
+\subsection{CVS versions} |
| 34 |
Portage has very crude support for CVS packages. The package \t{foo} could contain a file named |
| 35 |
\t{foo-cvs.1.2.3.ebuild}. This version would order \e{higher} than any non-CVS version (including |
| 36 |
\t{foo-2.ebuild}). This feature has not seen real world use and breaks versioned dependencies, so |
| 37 |
it must not be used. |
| 38 |
|
| 39 |
-\section{use.defaults} |
| 40 |
- |
| 41 |
+\subsection{use.defaults} |
| 42 |
The \t{use.defaults} file in the profile directory was used to implement `autouse'---switching USE |
| 43 |
flags on or off depending upon which packages are installed. It was deprecated long ago and finally |
| 44 |
removed in 2009. |
| 45 |
|
| 46 |
-\section{Old-style Virtuals} |
| 47 |
+\section{Retroactive Changes} |
| 48 |
+ |
| 49 |
+In some exceptional cases, changes to the specification have been approved by the Gentoo Council |
| 50 |
+without introducing a new EAPI. This section lists such retroactive changes. |
| 51 |
|
| 52 |
+\subsection{Old-style virtuals} |
| 53 |
Historically, virtuals were special packages rather than regular ebuilds. An ebuild could specify in |
| 54 |
the \t{PROVIDE} metadata that it supplied certain virtuals, and the package manager had to bear this |
| 55 |
in mind when handling dependencies. |
| 56 |
|
| 57 |
-Old-style virtuals were supported by EAPIs \t{0}, \t{1}, \t{2}, \t{3} and \t{4}, and were phased out |
| 58 |
-via GLEP 37~\cite{Glep37}. |
| 59 |
+Old-style virtuals were supported by EAPIs \t{0}, \t{1}, \t{2}, \t{3} and \t{4}. They were phased |
| 60 |
+out via GLEP 37~\cite{Glep37} and finally removed in 2011. |
| 61 |
|
| 62 |
% vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en : |
| 63 |
|
| 64 |
-- |
| 65 |
2.14.2 |
Archives