diff options
| author |   Ulrich Müller <ulm@gentoo.org> | 2020-04-11 11:56:39 +0200 |
|---|---|---|
| committer | Ulrich Müller <ulm@gentoo.org> | 2020-04-11 14:13:22 +0200 |
| commit | 58d5831ef7cc673858ea85d54ff0693f6a2f9914 (patch) | |
| tree | 2bfad9e3a04807e956ef9140dc7144a757e537ef | |
| parent | ebuild-functions.tex: Update array detection code. (diff) | |
| download | pms-58d5831ef7cc673858ea85d54ff0693f6a2f9914.tar.gz pms-58d5831ef7cc673858ea85d54ff0693f6a2f9914.tar.bz2 pms-58d5831ef7cc673858ea85d54ff0693f6a2f9914.zip | |
glossary.tex: Move explanation of new-style virtuals to the appendix.
The term "new-style virtual" is not used in the spec, so we need not
explain it in the glossary.
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
| -rw-r--r-- | appendices.tex | 4 | ||||
| -rw-r--r-- | glossary.tex | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/appendices.tex b/appendices.tex index ee537f7..21716d6 100644 --- a/appendices.tex +++ b/appendices.tex @@ -78,6 +78,10 @@ in mind when handling dependencies. Old-style virtuals were supported by EAPIs \t{0}, \t{1}, \t{2}, \t{3} and \t{4}. They were phased out via GLEP 37~\cite{Glep37} and finally removed in 2011. +\note{A `new-style virtual' is a normal package that installs no files and uses its dependency +requirements to pull in a `provider'. This does not require any special handling from the package +manager.} + \subsection{EAPI parsing} The method to specify the EAPI of an ebuild used to be a shell variable assignment, and the package manager had to source the ebuild in order to determine the EAPI\@. Therefore any ebuild using diff --git a/glossary.tex b/glossary.tex index 5666aa2..f8cd376 100644 --- a/glossary.tex +++ b/glossary.tex @@ -7,10 +7,6 @@ be immediately obvious. \begin{description} \item[qualified package name] A package name along with its associated category. For example, \t{app-editors/vim} is a qualified package name. -\item[new-style virtual] A new-style virtual is a normal package in the \t{virtual} category which - installs no files and uses its dependency requirements to pull in a `provider'. Historically, - old-style virtuals required special handling from the package manager; new-style virtuals do - not. \item[stand-alone repository] An (ebuild) repository which is intended to function on its own as the only, or primary, repository on a system. Contrast with \i{slave repository} below. \item[slave repository, non-stand-alone repository] An (ebuild) repository which is not complete |