commit: 571fb06ee654d9af7cc53772fb99adb70abac62e
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri May 6 17:23:31 2016 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri May 6 17:23:31 2016 +0000
URL: https://gitweb.gentoo.org/proj/pms.git/commit/?id=571fb06e
Typographic fix: Use compactitem rather than itemize.
ebuild-vars.tex | 4 ++--
pkg-mgr-commands.tex | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index 43ce528..1577e26 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -147,7 +147,7 @@ these values are different.
Keywords are used to indicate levels of stability of a package on a respective
architecture
\t{arch}. The following conventions are used:
-\begin{itemize}
+\begin{compactitem}
\item \t{arch}: Both the package version and the ebuild are widely tested,
known to work and not
have any serious issues on the indicated platform. This is referred to as
a \i{stable keyword}.
\item \t{\textasciitilde arch}: The package version and the ebuild are
believed to work and do
@@ -157,7 +157,7 @@ Keywords are used to indicate levels of stability of a
package on a respective a
\item No keyword: It is not known whether the package will work, or
insufficient testing has
occurred.
\item \t{-arch}: The package version will not work on the architecture.
-\end{itemize}
+\end{compactitem}
The \t{-*} keyword is used to indicate package versions which are not worth
trying to test on
unlisted architectures.
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
index be157cf..a8aa12b 100644
--- a/pkg-mgr-commands.tex
+++ b/pkg-mgr-commands.tex
@@ -834,14 +834,14 @@ has returned.
under the current working directory additionally have permissions \t{a+x}.
Arguments to \t{unpack} are interpreted as follows:
- \begin{itemize}
+ \begin{compactitem}
\item A filename without path (i.\,e., not containing any slash) is looked
up in \t{DISTDIR}.
\item An argument starting with the string \t{./} is a path relative to
the working directory.
\item \featurelabel{unpack-absolute} Otherwise, for EAPIs listed in
table~\ref{tab:unpack-behaviour} as supporting absolute and relative
paths, the argument is
interpreted as a literal path (absolute, or relative to the working
directory); for EAPIs
listed as \e{not} supporting such paths, \t{unpack} shall abort the
build process.
- \end{itemize}
+ \end{compactitem}
Any unrecognised file format shall be skipped silently. If unpacking a
supported file format
fails, \t{unpack} shall abort the build process.
