Summary: | portage-2.2_rc59 inconsistently uses an internal value of PATH and PATH from the environment during different phases | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kevin Wilson <kwilson> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kevin Wilson
2009-12-18 00:33:21 UTC
I didn't pay attention to all the details here, but I've adjusted the PATH handling in portage-2.1.7.16 and 2.2_rc61. Hopefully that solves your problem. Please test. Please reopen if this is still a problem. (In reply to comment #2) > Please reopen if this is still a problem. > (In reply to comment #1) > I didn't pay attention to all the details here, but I've adjusted the PATH > handling in portage-2.1.7.16 and 2.2_rc61. Hopefully that solves your problem. > Please test. > Thank you. I will test it soon. (In reply to comment #1) > I didn't pay attention to all the details here, but I've adjusted the PATH > handling in portage-2.1.7.16 and 2.2_rc61. Hopefully that solves your problem. > Please test. > It seems to work -- I just recompiled a set of 7 sci-physics/sci-libs packages with only PREROOTPATH set in my env files, and they all did what I expect. Thanks for the fix. You're welcome. |