...and explicitly state that it must not be set from within ebuilds/eclasses. Afais both portage and paludis already support this env variable. I'm not sure about pkgcore.
maybe even EXTRA_EMAKE...
(In reply to Julian Ospald (hasufell) from comment #0) > Afais both portage and paludis already support this env variable. I'm not > sure about pkgcore. pkgcore supports both EXTRA_ECONF and EXTRA_EMAKE set via profile or package.env since it inherited its bash code base from portage back in 2006 or whenever.
any interest here or can I close as DONTCARE?
It is a more general question if we want to add user configuration to PMS's scope. So far, section 1.1 says: "This document does not specify any user or package manager configuration information."
(In reply to Ulrich Müller from comment #4) > It is a more general question if we want to add user configuration to PMS's > scope. > > So far, section 1.1 says: > "This document does not specify any user or package manager configuration > information." I think the initial intention was just something like "ebuilds and eclasses must not set EXTRA_ECONF", which isn't particularly user configuration documentation, but it's debatable whether it belongs in the spec.
