1 |
commit: 54330c67cb6374e0bd704ea775871161ba7fdf72 |
2 |
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
3 |
AuthorDate: Sun Apr 25 21:20:55 2021 +0000 |
4 |
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
5 |
CommitDate: Fri Apr 30 16:24:30 2021 +0000 |
6 |
URL: https://gitweb.gentoo.org/proj/pms.git/commit/?id=54330c67 |
7 |
|
8 |
pms.cls: Do not define \e for \emph |
9 |
|
10 |
This is only used a few times, so a shorthand is not needed. |
11 |
(We really should get rid of \i and \t as well, because redefining |
12 |
LaTeX internal commands sucks.) |
13 |
|
14 |
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> |
15 |
|
16 |
appendices.tex | 2 +- |
17 |
dependencies.tex | 4 ++-- |
18 |
ebuild-env-state.tex | 2 +- |
19 |
ebuild-env-vars.tex | 2 +- |
20 |
ebuild-functions.tex | 2 +- |
21 |
introduction.tex | 4 ++-- |
22 |
pkg-mgr-commands.tex | 4 ++-- |
23 |
pms.cls | 1 - |
24 |
profiles.tex | 2 +- |
25 |
tree-layout.tex | 4 ++-- |
26 |
10 files changed, 13 insertions(+), 14 deletions(-) |
27 |
|
28 |
diff --git a/appendices.tex b/appendices.tex |
29 |
index 21716d6..3d2ef52 100644 |
30 |
--- a/appendices.tex |
31 |
+++ b/appendices.tex |
32 |
@@ -52,7 +52,7 @@ DEPEND=" |
33 |
|
34 |
\subsection{CVS versions} |
35 |
Portage has very crude support for CVS packages. The package \t{foo} could contain a file named |
36 |
-\t{foo-cvs.1.2.3.ebuild}. This version would order \e{higher} than any non-CVS version (including |
37 |
+\t{foo-cvs.1.2.3.ebuild}. This version would order \emph{higher} than any non-CVS version (including |
38 |
\t{foo-2.ebuild}). This feature has not seen real world use and breaks versioned dependencies, so |
39 |
it must not be used. |
40 |
|
41 |
|
42 |
diff --git a/dependencies.tex b/dependencies.tex |
43 |
index a641014..557ddce 100644 |
44 |
--- a/dependencies.tex |
45 |
+++ b/dependencies.tex |
46 |
@@ -377,8 +377,8 @@ Multiple requirements may be combined using commas, e.\,g.\ \t{[first,-second,th |
47 |
When multiple requirements are specified, all must match for a successful match. |
48 |
|
49 |
\featurelabel{use-dep-defaults} In a 4-style use dependency, the flag name may immediately be |
50 |
-followed by a \e{default} specified by either \t{(+)} or \t{(-)}. The former indicates that, when |
51 |
-applying the use dependency to a package that does not have the flag in question in |
52 |
+followed by a \emph{default} specified by either \t{(+)} or \t{(-)}. The former indicates that, |
53 |
+when applying the use dependency to a package that does not have the flag in question in |
54 |
\t{IUSE_REFERENCEABLE}, the package manager shall behave as if the flag were present and enabled; |
55 |
the latter, present and disabled. |
56 |
|
57 |
|
58 |
diff --git a/ebuild-env-state.tex b/ebuild-env-state.tex |
59 |
index 34c41c4..a998660 100644 |
60 |
--- a/ebuild-env-state.tex |
61 |
+++ b/ebuild-env-state.tex |
62 |
@@ -5,7 +5,7 @@ Exported and default scope variables are saved between functions. A non-local va |
63 |
function earlier in the call sequence must have its value preserved for later functions, including |
64 |
functions executed as part of a later uninstall. |
65 |
|
66 |
-\note{\t{pkg_pretend} is \e{not} part of the normal call sequence, and does not take part in |
67 |
+\note{\t{pkg_pretend} is \emph{not} part of the normal call sequence, and does not take part in |
68 |
environment saving.} |
69 |
|
70 |
Variables that were exported must remain exported in later functions; variables with default |
71 |
|
72 |
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex |
73 |
index 2736423..332c3d8 100644 |
74 |
--- a/ebuild-env-vars.tex |
75 |
+++ b/ebuild-env-vars.tex |
76 |
@@ -421,7 +421,7 @@ installing a package. Details are beyond the scope of this specification. |
77 |
|
78 |
\featurelabel{replace-version-vars} In EAPIs listed in table~\ref{tab:added-env-vars-table} as |
79 |
supporting it, the \t{REPLACING_VERSIONS} variable shall be defined in \t{pkg_preinst} and |
80 |
-\t{pkg_postinst}. In addition, it \e{may} be defined in \t{pkg_pretend} and \t{pkg_setup}, |
81 |
+\t{pkg_postinst}. In addition, it \emph{may} be defined in \t{pkg_pretend} and \t{pkg_setup}, |
82 |
although ebuild authors should take care to handle binary package creation and installation |
83 |
correctly when using it in these phases. |
84 |
|
85 |
|
86 |
diff --git a/ebuild-functions.tex b/ebuild-functions.tex |
87 |
index 3935800..ab3ed9c 100644 |
88 |
--- a/ebuild-functions.tex |
89 |
+++ b/ebuild-functions.tex |
90 |
@@ -24,7 +24,7 @@ Ebuilds must not call nor assume the existence of any phase functions. |
91 |
|
92 |
Some functions may assume that their initial working directory is set to a particular location; |
93 |
these are noted below. If no initial working directory is mandated, it may be set to anything and |
94 |
-the ebuild must not rely upon a particular location for it. The ebuild \e{may} assume that the |
95 |
+the ebuild must not rely upon a particular location for it. The ebuild \emph{may} assume that the |
96 |
initial working directory for any phase is a trusted location that may only be written to by a |
97 |
privileged user and group. |
98 |
|
99 |
|
100 |
diff --git a/introduction.tex b/introduction.tex |
101 |
index 8d1f793..b72acc3 100644 |
102 |
--- a/introduction.tex |
103 |
+++ b/introduction.tex |
104 |
@@ -5,7 +5,7 @@ |
105 |
This document aims to fully describe the format of an ebuild repository and the ebuilds therein, as |
106 |
well as certain aspects of package manager behaviour required to support such a repository. |
107 |
|
108 |
-This document is \e{not} designed to be an introduction to ebuild development. Prior knowledge of |
109 |
+This document is \emph{not} designed to be an introduction to ebuild development. Prior knowledge of |
110 |
ebuild creation and an understanding of how the package management system works is assumed; certain |
111 |
less familiar terms are explained in the Glossary in chapter~\ref{ch:glossary}. |
112 |
|
113 |
@@ -28,7 +28,7 @@ incompatibilities with any particular repository. |
114 |
\section{Reporting Issues} |
115 |
|
116 |
Issues (inaccuracies, wording problems, omissions etc.)\ in this document should be reported via |
117 |
-Gentoo Bugzilla using product \e{Gentoo Hosted Projects}, component \e{PMS/EAPI} and the default |
118 |
+Gentoo Bugzilla using product \i{Gentoo Hosted Projects}, component \i{PMS/EAPI} and the default |
119 |
assignee. There should be one bug per issue, and one issue per bug. |
120 |
|
121 |
Patches (in \t{git format-patch} form if possible) may be submitted either via Bugzilla or to the |
122 |
|
123 |
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex |
124 |
index b807117..59edc1c 100644 |
125 |
--- a/pkg-mgr-commands.tex |
126 |
+++ b/pkg-mgr-commands.tex |
127 |
@@ -184,7 +184,7 @@ completing. Ebuilds must not run any of these commands once the current phase fu |
128 |
a failure message provided in its first and only argument, and then aborts the build process. |
129 |
|
130 |
\featurelabel{subshell-die} In EAPIs listed in table~\ref{tab:die-properties} as not providing |
131 |
- subshell support, \t{die} is \e{not} guaranteed to work correctly if called from a subshell |
132 |
+ subshell support, \t{die} is \emph{not} guaranteed to work correctly if called from a subshell |
133 |
environment. |
134 |
\item[assert] Checks the value of the shell's pipe status variable, and if any component is non-zero |
135 |
(indicating failure), calls \t{die}, passing any parameters to it. |
136 |
@@ -1027,7 +1027,7 @@ has returned. |
137 |
\item \featurelabel{unpack-absolute} Otherwise, for EAPIs listed in |
138 |
table~\ref{tab:unpack-behaviour} as supporting absolute and relative paths, the argument is |
139 |
interpreted as a literal path (absolute, or relative to the working directory); for EAPIs |
140 |
- listed as \e{not} supporting such paths, \t{unpack} shall abort the build process. |
141 |
+ listed as \emph{not} supporting such paths, \t{unpack} shall abort the build process. |
142 |
\end{compactitem} |
143 |
|
144 |
Any unrecognised file format shall be skipped silently. If unpacking a supported file format |
145 |
|
146 |
diff --git a/pms.cls b/pms.cls |
147 |
index d7c6ed8..ee0d60f 100644 |
148 |
--- a/pms.cls |
149 |
+++ b/pms.cls |
150 |
@@ -110,7 +110,6 @@ |
151 |
\renewcommand{\i}[1]{\textit{#1}} |
152 |
\renewcommand{\t}[1]{\texttt{#1}} |
153 |
} |
154 |
-\newcommand{\e}[1]{\emph{#1}} |
155 |
\newcommand{\note}[1]{\begin{trivlist}\item\textbf{Note:} #1\end{trivlist}} |
156 |
|
157 |
% Because we are lazy, we define a table environment to fulfil our needs |
158 |
|
159 |
diff --git a/profiles.tex b/profiles.tex |
160 |
index 76c9278..a3e666e 100644 |
161 |
--- a/profiles.tex |
162 |
+++ b/profiles.tex |
163 |
@@ -40,7 +40,7 @@ If a profile contains a file named \t{deprecated}, it is treated as such. The fi |
164 |
file should contain the path from the \t{profiles} directory of the repository to a valid profile |
165 |
that is the recommended upgrade path from this profile. The remainder of the file can contain any |
166 |
text, which may be displayed to users using this profile by the package manager. This file is not |
167 |
-inherited---profiles which inherit from a deprecated profile are \e{not} deprecated. |
168 |
+inherited---profiles which inherit from a deprecated profile are \emph{not} deprecated. |
169 |
|
170 |
This file must not contain comments or make use of line continuations. |
171 |
|
172 |
|
173 |
diff --git a/tree-layout.tex b/tree-layout.tex |
174 |
index 80d70d6..138e533 100644 |
175 |
--- a/tree-layout.tex |
176 |
+++ b/tree-layout.tex |
177 |
@@ -35,7 +35,7 @@ the category. Each category directory shall contain: |
178 |
\end{compactitem} |
179 |
|
180 |
Category directories may contain additional files, whose purpose is not covered by this |
181 |
-specification. Additional directories that are not for a package may \e{not} be present, to avoid |
182 |
+specification. Additional directories that are not for a package may \emph{not} be present, to avoid |
183 |
conflicts with package name directories; an exception is made for filesystem components whose name |
184 |
starts with a dot, which the package manager must ignore, and for any directory named \t{CVS}. |
185 |
|
186 |
@@ -120,7 +120,7 @@ manager must ignore any files in this directory that it does not recognise. |
187 |
\item[desc/] This directory contains files analogous to \t{use.desc} for the various \t{USE_EXPAND} |
188 |
variables. Each file in it is named \t{<varname>.desc}, where \t{<varname>} is the variable |
189 |
name, in lowercase, whose possible values the file describes. The format of each file is as for |
190 |
- \t{use.desc}, described in section~\ref{sec:use.desc}. The \t{USE_EXPAND} name is \e{not} |
191 |
+ \t{use.desc}, described in section~\ref{sec:use.desc}. The \t{USE_EXPAND} name is \emph{not} |
192 |
included as a prefix here. |
193 |
\item[updates/] This directory is described in section~\ref{sec:updates-dir}. |
194 |
\end{description} |