Summary: | binpkg wierdness, wrong sourcing | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Simon Stelling (RETIRED) <blubb> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Simon Stelling (RETIRED)
2006-03-07 12:15:06 UTC
I came across this one while working on my tinderbox setup. Don't know if I remember correctly, but it's because ${T} is set and contains an old environment file, which is sourced by ebuild.sh. The old environment overrides EBUILD and the sourcing of the ebuild fails. I fixed it by: --- ebuild.sh.orig 2006-03-07 20:29:41.877561651 +0000 +++ ebuild.sh 2006-02-14 11:33:04.025289539 +0000 @@ -11,7 +11,7 @@ SANDBOX_PREDICT="${SANDBOX_PREDICT}:${PORTAGE_GPG_DIR}" fi -if [ "$*" != "depend" ] && [ "$*" != "clean" ] && [ "$*" != "nofetch" ]; then +if [ "$*" != "depend" ] && [ "$*" != "clean" ] && [ "$*" != "nofetch" ] && [ "$*" != "setup" ]; then if [ -f "${T}/environment" ]; then source "${T}/environment" &>/dev/null fi |