Bug 540146

Summary:	sys-apps/portage: limit no of exported variables in EAPI 6
Product:	Portage Development	Reporter:	Michał Górny <mgorny>
Component:	Core - Ebuild Support	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	normal	CC:	kingjon3377, pacho, pms, sam
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=414955 https://bugs.gentoo.org/show_bug.cgi?id=721088
Whiteboard:
Package list:		Runtime testing required:	---

Description Michał Górny archtester

2015-02-15 13:38:38 UTC

Right now, Portage exports a lot of internal ebuild variables to spawned programs. This is bad for two reasons:

1. it breaks programs which use same-named environment variables for different purpose,

2. it allows developers to rely on them being exported while PMS doesn't guarantee that (and often doesn't even guarantee them having any sane value during ebuild run).

I think it'd be a good idea to start removing export bits on those variables whenever possible in EAPI 6. This will keep existing ebuilds working while preventing future reliance on this non-PMS behavior. However, we might need to employ some more IPC between some of the ebuild helpers and Portage to avoid requiring the variables being exported.

CC-ing pms-bugs@ for confirmation/opinion.