Bug 365439 – Add optional possibility of overriding variables set in /etc/portage/env by variables exported in parent environment

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Arfrever Frehtes Taifersar Arahesis (RETIRED) 2011-04-30 17:51:09 UTC]

Variables exported in parent environment override variables set in /etc/make.conf, but don't override variables set in /etc/portage/env.

Example:
VARIABLE="value" emerge ${package}

[Comment 1 Zac Medico 2011-04-30 18:22:47 UTC]

Is this about package.env or /etc/portage/env bashrc? I ask since there's nothing that we can do about bashrc, since bashrc is always supposed to override everything else.

[Comment 2 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2011-05-01 01:26:42 UTC]

set_unless_changed() and unset_unless_changed() helper functions have been added (after a discussion in IRC):
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=81354e43b5acf25cadc42f6c093d52acf8f832fb

[Comment 3 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2011-05-01 14:54:23 UTC]

Minor improvements:
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=693681562c7795473efd0caaa05b8d52b28f75db

[Comment 4 Zac Medico 2011-05-05 19:54:18 UTC]

This is fixed in 2.1.9.47 and 2.2.0_alpha31.

[Comment 5 Zac Medico 2011-05-28 07:47:20 UTC]

*** Bug 368901 has been marked as a duplicate of this bug. ***