The spec currently says: > Except where otherwise noted, all variables set in the active profiles’ make.defaults files must be exported to the ebuild environment. Let's limit this to variables that don't have special meaning such as USE and specific variables defined by USE_EXPAND. Particularly, ARCH is known to cause accidental breakage.
First draft posted to gentoo-pms: https://public-inbox.gentoo.org/gentoo-pms/20250114110252.4720-1-ulm@gentoo.org/
@Council: This is an addendum to the feature that we approved in the 2025-01-12 meeting. In addition to the variables defined by the package manager, also the variables listed in section 5.3.2 of the spec would stop being exported. The complete list is: ARCH CONFIG_PROTECT CONFIG_PROTECT_MASK USE USE_EXPAND USE_EXPAND_UNPREFIXED USE_EXPAND_HIDDEN USE_EXPAND_IMPLICIT IUSE_IMPLICIT ENV_UNSET All variables named in USE_EXPAND and USE_EXPAND_UNPREFIXED USE_EXPAND_VALUES_${v}, where ${v} is a value in USE_EXPAND_IMPLICIT Motion: Special profile variables (namely those listed in section 5.3.2 "Specific variables and their meanings") are no longer exported to the environment in EAPI 9. Please vote.
I vote yes.
yes
Accepted unanimously (7 yes, 0 no, 0 abstentions).
Note that the ABI variable is _not_ in the list from comment #2. The spec says elsewhere that ABI is supposed to be an environment variable, e.g. in algorithm 12.4: https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-136025r4
