Summary: | /etc/profile.env vars override local enviroment variables | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robin Johnson <robbat2> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robin Johnson
2004-05-20 04:33:03 UTC
as a further note, older versions of portage do this correctly, as the app-admin/amanda package used to rely on it and work perfectly when I originally wrote it. *** This bug has been marked as a duplicate of 51095 *** Jason: they are not the same! the changes listed under that bug only provide a special environment for portage. i want emerge to use the environment present when it is run, which is NOT the same as the contents as profile*, .bashrc, et al, as I've set environment variables locally. the closest thing is the mention of 'It should go after CC/CXX are saved and restored from sourcing profile.env, because the admin may wish to override CC for a particular package in /etc/portage/bashrc.' I want practially all variables to have the same behavior as CC/CXX. That's not easy in the least... Although it semi-reasonable... carpaski: i don't see it as that difficult at all. at the very start of emerge, it should capture the enviroment in place. 1. printenv > tmpfile (this needs to be done as early as possible) 2. source /etc/profile, /etc/portage/bashrc etc. 3. remove all special items from tmpfile (just use egrep -v) 4. eval `cat tmpfile` 5. you may want to save this environment now so it can be re-used faster instead of re-doing the above. Robin: Apologies. The bugs are definately related though. any progress on this? *bump* *bump back* Nick, the daemon fixes this (fyi)... Just testing again, this seems to work as of 2.0.51.22-r1 Erm, not really fixed. *** This bug has been marked as a duplicate of 51370 *** |