Summary: | env-update doenst update working environment | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bernardo S. A. Silva <bernardos> |
Component: | [OLD] Core system | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.4_rc1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bernardo S. A. Silva
2002-12-27 20:37:00 UTC
part #1 is valid, part #2 is a bug thats already open A program cannot modify it's parent environment. Apps cannot update the variables auotmatically that way. You can always '. /etc/profile' or 'source /etc/profile' when you or portage runs env-update. Part #2 is a bug thats already open... ok, but what his number? Part #1: Why the gcc-config doesn't make the source automatic? Thanx... Bernardo S. A. Silva So... I will reopen it... A program cannot modify it's parent environment. Therefore... It can't cause the new variables to propagate up to the parents, and thus cannot, due to unix system implimentations, be automatic as you'd like. There are a couple bugs floating around on that other topic. It's coming... 'Sticky.' |