Cheat sheet: Remove EAPI 5 to make room for EAPI 8

Signed-off-by: Ulrich Müller <ulm@gentoo.org>

1 files changed, 70 insertions, 70 deletions

diff --git a/eapi-cheatsheet.tex b/eapi-cheatsheet.tex
index fb62827..82602f2 100644
--- a/eapi-cheatsheet.tex
+++ b/eapi-cheatsheet.tex
@@ -77,7 +77,7 @@
     \footnote{\url{https://creativecommons.org/licenses/by-sa/4.0/}}
 \end{abstract}
 
-\section{EAPIs 0, 1, 2, 3, and 4}
+\section{EAPIs 0, 1, 2, 3, 4, and 5}
 \label{sec:cs:eapi0-2}
 Omitted for lack of space. See version~5.0 of this document for
 differences between these previous EAPIs.
@@ -257,75 +257,75 @@ differences between these previous EAPIs.
 %     any more.  See \featureref{aa} and \featureref{kv}.
 % \end{description}
 
-\section{EAPI 5 (2012-09-20)}
-\label{sec:cs:eapi5}
-\subsection{Additions/Changes}
-\label{sec:cs:eapi5-additions}
-\begin{description}
-    \item[Sub-slots] The \code{SLOT} variable and slot dependencies
-    may contain an optional sub-slot part that follows the regular
-    slot, delimited by a \code{/} character; for example
-    \code{2/2.30}.  The sub-slot is used to represent cases in which
-    an upgrade to a new version of a package with a different sub-slot
-    may require dependent packages to be rebuilt.  If the sub-slot is
-    not specified in \code{SLOT}, it defaults to the regular slot.
-    See \featureref{sub-slot}.
-    \item[Slot operator dependencies] Package dependencies can specify
-    one of the following operators as a suffix, which will affect
-    updates of runtime dependencies:
-    \begin{description}
-        \item[\code{:*}] Any slot value is acceptable.  The package
-        will not break when its dependency is updated.
-        \item[\code{:=}] Any slot value is acceptable, but the package
-        can break when its dependency is updated to a different slot
-        (or sub-slot).
-    \end{description}
-    See \featureref{slot-operator-deps}.
-    \item[Profile \code{IUSE} injection] Apart from the USE flags
-    explicitly listed in \code{IUSE}, additional flags can be
-    implicitly provided by profiles.
-    See \featureref{profile-iuse-inject}.
-    \item[At-most-one-of groups] In \code{REQUIRED_USE} you can use
-    "\code{??\ ( flag1 flag2 \dots\ )}" to allow zero or one USE flag
-    out of many.
-    See \featureref{at-most-one-of}.
-    \item[Parallel tests] The default for \code{src_test} runs
-    \code{emake} without \code{-j1} now.
-    See \featureref{parallel-tests}.
-    \item[\code{econf} changes] The \code{econf} function now always
-    passes \code{-{}-disable-silent-rules} to \code{configure}.
-    See \featureref{econf-options}.
-    \item[\code{has_version} and \code{best_version} changes]
-    The two helpers support a \code{-{}-host-root} option that causes
-    the query to apply to the host root instead of \code{ROOT}.
-    See~\featureref{pm-query-options}.
-    \item[\code{usex}] Usage for this helper function is
-    \code{usex} \emph{<USE flag> [true1] [false1] [true2] [false2]}.
-    If the USE flag is set, outputs \emph{[true1][true2]}
-    (defaults to \code{yes}), otherwise outputs
-    \emph{[false1][false2]} (defaults to \code{no}).
-    See \featureref{usex}.
-    \item[\code{doheader} and \code{newheader}] These new helper
-    functions install the given header file(s) into
-    \code{/usr/include}. The \code{-r} option enables recursion for
-    \code{doheader}, similar to \code{doins}.
-    See \featureref{doheader}.
-    \item[\code{new*} standard input] The \code{newins} etc.\ commands
-    read from standard input if the first argument is \code{-}
-    (a hyphen).
-    See \featureref{newfoo-stdin}.
-    \item[\code{EBUILD_PHASE_FUNC}] This variable is very similar to
-    \code{EBUILD_PHASE}, but contains the name of the current ebuild
-    function.
-    See \featureref{ebuild-phase-func}.
-    \item[Stable use masking/forcing] New files
-    \code{use.stable.\allowbreak\{mask,force\}} and
-    \code{package.use.stable.\allowbreak\{mask,force\}}
-    are supported in profile directories.  They are similar to their
-    non-\code{stable} counterparts, but act only on packages that
-    would be merged due to a stable keyword.
-    See \featureref{stablemask}.
-\end{description}
+% \section{EAPI 5 (2012-09-20)}
+% \label{sec:cs:eapi5}
+% \subsection{Additions/Changes}
+% \label{sec:cs:eapi5-additions}
+% \begin{description}
+%     \item[Sub-slots] The \code{SLOT} variable and slot dependencies
+%     may contain an optional sub-slot part that follows the regular
+%     slot, delimited by a \code{/} character; for example
+%     \code{2/2.30}.  The sub-slot is used to represent cases in which
+%     an upgrade to a new version of a package with a different sub-slot
+%     may require dependent packages to be rebuilt.  If the sub-slot is
+%     not specified in \code{SLOT}, it defaults to the regular slot.
+%     See \featureref{sub-slot}.
+%     \item[Slot operator dependencies] Package dependencies can specify
+%     one of the following operators as a suffix, which will affect
+%     updates of runtime dependencies:
+%     \begin{description}
+%         \item[\code{:*}] Any slot value is acceptable.  The package
+%         will not break when its dependency is updated.
+%         \item[\code{:=}] Any slot value is acceptable, but the package
+%         can break when its dependency is updated to a different slot
+%         (or sub-slot).
+%     \end{description}
+%     See \featureref{slot-operator-deps}.
+%     \item[Profile \code{IUSE} injection] Apart from the USE flags
+%     explicitly listed in \code{IUSE}, additional flags can be
+%     implicitly provided by profiles.
+%     See \featureref{profile-iuse-inject}.
+%     \item[At-most-one-of groups] In \code{REQUIRED_USE} you can use
+%     "\code{??\ ( flag1 flag2 \dots\ )}" to allow zero or one USE flag
+%     out of many.
+%     See \featureref{at-most-one-of}.
+%     \item[Parallel tests] The default for \code{src_test} runs
+%     \code{emake} without \code{-j1} now.
+%     See \featureref{parallel-tests}.
+%     \item[\code{econf} changes] The \code{econf} function now always
+%     passes \code{-{}-disable-silent-rules} to \code{configure}.
+%     See \featureref{econf-options}.
+%     \item[\code{has_version} and \code{best_version} changes]
+%     The two helpers support a \code{-{}-host-root} option that causes
+%     the query to apply to the host root instead of \code{ROOT}.
+%     See~\featureref{pm-query-options}.
+%     \item[\code{usex}] Usage for this helper function is
+%     \code{usex} \emph{<USE flag> [true1] [false1] [true2] [false2]}.
+%     If the USE flag is set, outputs \emph{[true1][true2]}
+%     (defaults to \code{yes}), otherwise outputs
+%     \emph{[false1][false2]} (defaults to \code{no}).
+%     See \featureref{usex}.
+%     \item[\code{doheader} and \code{newheader}] These new helper
+%     functions install the given header file(s) into
+%     \code{/usr/include}. The \code{-r} option enables recursion for
+%     \code{doheader}, similar to \code{doins}.
+%     See \featureref{doheader}.
+%     \item[\code{new*} standard input] The \code{newins} etc.\ commands
+%     read from standard input if the first argument is \code{-}
+%     (a hyphen).
+%     See \featureref{newfoo-stdin}.
+%     \item[\code{EBUILD_PHASE_FUNC}] This variable is very similar to
+%     \code{EBUILD_PHASE}, but contains the name of the current ebuild
+%     function.
+%     See \featureref{ebuild-phase-func}.
+%     \item[Stable use masking/forcing] New files
+%     \code{use.stable.\allowbreak\{mask,force\}} and
+%     \code{package.use.stable.\allowbreak\{mask,force\}}
+%     are supported in profile directories.  They are similar to their
+%     non-\code{stable} counterparts, but act only on packages that
+%     would be merged due to a stable keyword.
+%     See \featureref{stablemask}.
+% \end{description}
 
 \section{EAPI 6 (2015-11-13)}
 \label{sec:cs:eapi6}