* [gentoo-pms] [PATCH] Clarify that USE_EXPAND variables are exported
@ 2024-12-02 23:14 Ulrich Müller
2024-12-03 0:25 ` Sam James
0 siblings, 1 reply; 2+ messages in thread
From: Ulrich Müller @ 2024-12-02 23:14 UTC (permalink / raw
To: gentoo-pms; +Cc: Ulrich Müller
Closes: https://bugs.gentoo.org/945538
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
profile-variables.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/profile-variables.tex b/profile-variables.tex
index 9f86e80..f1c03de 100644
--- a/profile-variables.tex
+++ b/profile-variables.tex
@@ -78,9 +78,9 @@ The following variables have specific meanings when set in profiles.
configuration file protection. Described more fully in section~\ref{sec:config-protect}.
\item[USE] Defines the list of default USE flags for this profile. Flags may be added or removed by
the user's configuration. \t{USE_EXPAND} values must not be specified in this way.
-\item[USE_EXPAND] Defines a list of variables which are to be treated incrementally and whose
- contents are to be expanded into the USE variable as passed to ebuilds. See
- section~\ref{sec:use-iuse-handling} for details.
+\item[USE_EXPAND] Defines a list of variables which are to be treated incrementally, exported to
+ the ebuild environment, and whose contents are to be expanded into the USE variable as passed
+ to ebuilds. See section~\ref{sec:use-iuse-handling} for details.
\item[USE_EXPAND_UNPREFIXED] Similar to \t{USE_EXPAND}, but no prefix is used. If the repository
contains any package using an EAPI supporting profile-defined \t{IUSE} injection (see
table~\ref{tab:profile-iuse-injection-table}), this list must contain at least \t{ARCH}\@.
--
2.47.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [gentoo-pms] [PATCH] Clarify that USE_EXPAND variables are exported
2024-12-02 23:14 [gentoo-pms] [PATCH] Clarify that USE_EXPAND variables are exported Ulrich Müller
@ 2024-12-03 0:25 ` Sam James
0 siblings, 0 replies; 2+ messages in thread
From: Sam James @ 2024-12-03 0:25 UTC (permalink / raw
To: Ulrich Müller; +Cc: gentoo-pms
Ulrich Müller <ulm@gentoo.org> writes:
> Closes: https://bugs.gentoo.org/945538
> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
LGTM and thanks.
Reviewed-by: Sam James <sam@gentoo.org>
> ---
> profile-variables.tex | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/profile-variables.tex b/profile-variables.tex
> index 9f86e80..f1c03de 100644
> --- a/profile-variables.tex
> +++ b/profile-variables.tex
> @@ -78,9 +78,9 @@ The following variables have specific meanings when set in profiles.
> configuration file protection. Described more fully in section~\ref{sec:config-protect}.
> \item[USE] Defines the list of default USE flags for this profile. Flags may be added or removed by
> the user's configuration. \t{USE_EXPAND} values must not be specified in this way.
> -\item[USE_EXPAND] Defines a list of variables which are to be treated incrementally and whose
> - contents are to be expanded into the USE variable as passed to ebuilds. See
> - section~\ref{sec:use-iuse-handling} for details.
> +\item[USE_EXPAND] Defines a list of variables which are to be treated incrementally, exported to
> + the ebuild environment, and whose contents are to be expanded into the USE variable as passed
> + to ebuilds. See section~\ref{sec:use-iuse-handling} for details.
> \item[USE_EXPAND_UNPREFIXED] Similar to \t{USE_EXPAND}, but no prefix is used. If the repository
> contains any package using an EAPI supporting profile-defined \t{IUSE} injection (see
> table~\ref{tab:profile-iuse-injection-table}), this list must contain at least \t{ARCH}\@.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-12-03 0:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-12-02 23:14 [gentoo-pms] [PATCH] Clarify that USE_EXPAND variables are exported Ulrich Müller
2024-12-03 0:25 ` Sam James
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox