commit:     4f5225a94cf3207a3857efe009f18283f142f148
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 13 21:14:36 2025 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Dec  2 19:05:21 2025 +0000
URL:        https://gitweb.gentoo.org/proj/pms.git/commit/?id=4f5225a9

EAPI 9: Special profile variables are no longer exported

Bug: https://bugs.gentoo.org/948001
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 ebuild-env-vars.tex   | 12 ++++++++----
 profile-variables.tex |  2 ++
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index 434cef9..5a59590 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -18,6 +18,12 @@ unexported shell variables, as specified for EAPIs in 
table~\ref{tab:export-vars
 the package manager must pass those that are required by ebuild-specific 
external commands
 (see section~\ref{sec:pkg-mgr-commands}) in an implementation-defined manner.
 
+Variables listed in section~\ref{sec:specific-profile-vars} as having specific 
meanings or special
+handling, and that are set in the active profiles' \t{make.defaults} files, 
obey the same export
+rules specified for EAPIs in table~\ref{tab:export-vars}. This behaviour is 
governed by the EAPI
+of the ebuild, not that of the profile. Except where otherwise noted, all 
other variables set in
+the active profiles' \t{make.defaults} files must be exported to the 
environment.
+
 \ChangeWhenAddingAnEAPI{9}
 \begin{centertable}{EAPIs with variables exported to the environment}
     \label{tab:export-vars}
@@ -354,10 +360,8 @@ the package manager must pass those that are required by 
ebuild-specific externa
     \end{tabular}
 \end{centertable}
 
-Except where otherwise noted, all variables set in the active profiles' 
\t{make.defaults} files must
-be exported to the ebuild environment. \t{CHOST}, \t{CBUILD} and \t{CTARGET}, 
if not set by
-profiles, must contain either an appropriate machine tuple (the definition of 
appropriate is beyond
-the scope of this specification) or be unset.
+\t{CHOST}, \t{CBUILD} and \t{CTARGET}, if not set by profiles, must contain 
either an appropriate
+machine tuple (the definition of appropriate is beyond the scope of this 
specification) or be unset.
 
 \t{PATH} must be initialized by the package manager to a ``usable'' default.  
The exact value here
 is left up to interpretation, but it should include the equivalent ``sbin'' 
and ``bin'' and any

diff --git a/profile-variables.tex b/profile-variables.tex
index f20fde4..ddcbd3a 100644
--- a/profile-variables.tex
+++ b/profile-variables.tex
@@ -69,6 +69,8 @@ completely override those in parent profiles.
 \end{centertable}
 
 \subsection{Specific variables and their meanings}
+\label{sec:specific-profile-vars}
+
 The following variables have specific meanings when set in profiles.
 \begin{description}
 \item[ARCH] The system's architecture. Must be a value listed in 
\t{profiles/arch.list}; see

Reply via email to