Summary: | GLEP 47: Creating 'safe' environment variables | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | alt, radek |
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/proj/en/glep/glep-0047.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Diego Elio Pettenò (RETIRED)
2005-10-06 13:50:48 UTC
Profile bashrc's don't affect the python side of portage at all, at the moment. Hence, it couldn't be used immediately. I definitely like this much more than GLEP22 though. ;) Speaking of which, how would this work with ebuild keywording? Just a little side-note, GNU/kFreeBSD carries version info in the triplet, e.g. x86_64-pc-kfreebsd5.4-gnu So instead of *-*-kfreebsd-gnu, you need *-*-kfreebsd*-gnu. Btw, why do you need this "readmap" thing. Can't these variables in /etc/make.conf just be made mandatory? It doesn't even need to be mandatory for all platforms, if you assume that non-existance of the vars implies *-*-linux-gnu. The point of all this is to make sure that they are not tricked by users breaking systems in untoldable ways. I think this is just waiting for the new GLEP to be presented, discussed and, hopefully, accepted. What's the status on this? Mind that if this is supposed to affect $USE (via USE_EXPAND) you can't use a bash solution (as mentioned in comment #1) and I don't see this restriction changing anytime soon. Anyone still going for this? closing due to apparent lack of interest |