|
Lines 70-88
parent profile's list is taken, and the current profile's list appended. If any
Link Here
|
| 70 |
hyphen, then any lines previous to it whose contents are equal to the remainder of that line are |
70 |
hyphen, then any lines previous to it whose contents are equal to the remainder of that line are |
| 71 |
removed from the list. Once again, blank lines and those beginning with a \# are discarded. |
71 |
removed from the list. Once again, blank lines and those beginning with a \# are discarded. |
| 72 |
|
72 |
|
| 73 |
\subsection{packages} |
73 |
For EAPIs listed as supported in table~\ref{tab:profile-packagemask}, simple line-based files described in |
|
|
74 |
the following sectionss may optionally be directories containing files of the named type. |
| 75 |
|
| 76 |
\ChangeWhenAddingAnEAPI{6} |
| 77 |
\begin{centertable}{Profile support for directories of simple line-based files}\label{tab:profile-packagemask} |
| 78 |
\begin{tabular}{ l l l } |
| 79 |
\toprule |
| 80 |
\multicolumn{1}{c}{\textbf{EAPI}} & |
| 81 |
\multicolumn{1}{c}{\textbf{Supports directories of simple line-based files}} \\ |
| 82 |
\midrule |
| 83 |
\t{0} & No \\ |
| 84 |
\t{1} & No \\ |
| 85 |
\t{2} & No \\ |
| 86 |
\t{3} & No \\ |
| 87 |
\t{4} & No \\ |
| 88 |
\t{5} & No \\ |
| 89 |
\t{6} & Yes \\ |
| 90 |
\bottomrule |
| 91 |
\end{tabular} |
| 92 |
\end{centertable} |
| 93 |
|
| 94 |
\subsubsection{packages} |
| 74 |
The \t{packages} file is used to define the `system set' for this profile. |
95 |
The \t{packages} file is used to define the `system set' for this profile. |
| 75 |
After the above rules for inheritance and comments are applied, its lines must take one of two |
96 |
After the above rules for inheritance and comments are applied, its lines must take one of two |
| 76 |
forms: a package dependency specification prefixed by \t{*} denotes that the atom forms part of the |
97 |
forms: a package dependency specification prefixed by \t{*} denotes that the atom forms part of the |
| 77 |
system set. A package dependency specification on its own may also appear for legacy reasons, but |
98 |
system set. A package dependency specification on its own may also appear for legacy reasons, but |
| 78 |
should be ignored when calculating the system set. |
99 |
should be ignored when calculating the system set. |
| 79 |
|
100 |
|
| 80 |
\subsection{packages.build} |
101 |
\subsubsection{packages.build} |
| 81 |
The \t{packages.build} file is used by Gentoo's Catalyst tool to generate stage1 tarballs, and has |
102 |
The \t{packages.build} file is used by Gentoo's Catalyst tool to generate stage1 tarballs, and has |
| 82 |
no relevance to the operation of a package manager. It is thus outside the scope of this document, |
103 |
no relevance to the operation of a package manager. It is thus outside the scope of this document, |
| 83 |
but is mentioned here for completeness. |
104 |
but is mentioned here for completeness. |
| 84 |
|
105 |
|
| 85 |
\subsection{package.mask} |
106 |
\note At the time of writing, Catalyst does not support packages.build as a directory. |
|
|
107 |
|
| 108 |
\subsubsection{package.mask} |
| 86 |
\t{package.mask} is used to prevent packages from being installed on a given profile. Each line |
109 |
\t{package.mask} is used to prevent packages from being installed on a given profile. Each line |
| 87 |
contains one package dependency specification; anything matching this specification will not be |
110 |
contains one package dependency specification; anything matching this specification will not be |
| 88 |
installed unless unmasked by the user's configuration. |
111 |
installed unless unmasked by the user's configuration. |
|
Lines 93-112
necessarily a global mask (from \t{profiles/package.mask}, section~\ref{profiles
Link Here
|
| 93 |
\note Portage currently treats \t{profiles/package.mask} as being on the leftmost branch of the |
116 |
\note Portage currently treats \t{profiles/package.mask} as being on the leftmost branch of the |
| 94 |
inherit tree when it comes to \t{-lines}. This behaviour may not be relied upon. |
117 |
inherit tree when it comes to \t{-lines}. This behaviour may not be relied upon. |
| 95 |
|
118 |
|
| 96 |
\subsection{package.provided} |
119 |
\subsubsection{package.provided} |
| 97 |
\t{package.provided} is used to tell the package manager that a certain package version should be |
120 |
\t{package.provided} is used to tell the package manager that a certain package version should be |
| 98 |
considered to be provided by the system regardless of whether it is actually installed. Because it |
121 |
considered to be provided by the system regardless of whether it is actually installed. Because it |
| 99 |
has severe adverse effects on USE-based and slot-based dependencies, its use is strongly deprecated |
122 |
has severe adverse effects on USE-based and slot-based dependencies, its use is strongly deprecated |
| 100 |
and package manager support must be regarded as purely optional. |
123 |
and package manager support must be regarded as purely optional. |
| 101 |
|
124 |
|
| 102 |
\subsection{package.use} |
125 |
\subsubsection{package.use} |
| 103 |
The \t{package.use} file may be used by the package manager to override the default USE flags specified |
126 |
The \t{package.use} file may be used by the package manager to override the default USE flags specified |
| 104 |
by \t{make.defaults} on a per package basis. The format is to have a package dependency specification, |
127 |
by \t{make.defaults} on a per package basis. The format is to have a package dependency specification, |
| 105 |
and then a space delimited list of USE flags to enable. A USE flag in the form of \t{-flag} indicates |
128 |
and then a space delimited list of USE flags to enable. A USE flag in the form of \t{-flag} indicates |
| 106 |
that the package should have the USE flag disabled. The package dependency specification is limited to |
129 |
that the package should have the USE flag disabled. The package dependency specification is limited to |
| 107 |
the forms defined by the directory's EAPI. |
130 |
the forms defined by the directory's EAPI. |
| 108 |
|
131 |
|
| 109 |
\subsection{USE masking and forcing} |
132 |
\subsubsection{USE masking and forcing} |
| 110 |
\label{sec:use-masking} |
133 |
\label{sec:use-masking} |
| 111 |
This section covers the eight files \t{use.mask}, \t{use.force}, \t{use.stable.mask}, |
134 |
This section covers the eight files \t{use.mask}, \t{use.force}, \t{use.stable.mask}, |
| 112 |
\t{use.stable.force}, \t{package.use.mask}, \t{package.use.force}, \t{package.use.stable.mask}, |
135 |
\t{use.stable.force}, \t{package.use.mask}, \t{package.use.force}, \t{package.use.stable.mask}, |
| 113 |
- |
|
|
