Summary: | sys-apps/portage-2.1.9.3 forces CONFIG_PROTECT_MASK=/etc/portage | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andrew Church <achurch+gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrew Church
2010-09-11 02:21:35 UTC
I think it's just leaking in from your shell environment and you need to source /etc/profile. Try this: echo $CONFIG_PROTECT_MASK source /etc/profile echo $CONFIG_PROTECT_MASK Right you are -- sorry! (Though it seems odd that CONFIG_PROTECT_MASK should be exported to the environment; is there a reason for that?) It's just a side effect from the earlier portage-2.1.9.x ebuild setting in via /etc/env.d/. Anything that's set in /etc/env.d/ gets exported by /etc/profile. Ah, I see -- thanks for the clarification. I'll go ahead and close this as INVALID. |