Don't use sandbox's BASH_ENV for new shells because it does
authorZac Medico <zmedico@gentoo.org>
Fri, 30 Nov 2007 09:03:00 +0000 (09:03 -0000)
committerZac Medico <zmedico@gentoo.org>
Fri, 30 Nov 2007 09:03:00 +0000 (09:03 -0000)
'source /etc/profile' which can interfere with the build
environment by modifying our PATH.

svn path=/main/trunk/; revision=8761

bin/ebuild.sh

index f8f7377d7f40bbc1976bd59c6ed2265df806bfca..78c423278690748edb872d1e84943b9113f70e98 100755 (executable)
@@ -10,6 +10,10 @@ SANDBOX_PREDICT="${SANDBOX_PREDICT}:/proc/self/maps:/dev/console:/dev/random"
 export SANDBOX_PREDICT="${SANDBOX_PREDICT}:${PORTAGE_PYM_PATH}:${PORTAGE_DEPCACHEDIR}"
 export SANDBOX_WRITE="${SANDBOX_WRITE}:/dev/shm:/dev/stdout:/dev/stderr:${PORTAGE_TMPDIR}"
 export SANDBOX_READ="${SANDBOX_READ}:/dev/shm:/dev/stdin:${PORTAGE_TMPDIR}"
+# Don't use sandbox's BASH_ENV for new shells because it does
+# 'source /etc/profile' which can interfere with the build
+# environment by modifying our PATH.
+unset BASH_ENV
 
 if [ ! -z "${PORTAGE_GPG_DIR}" ]; then
        SANDBOX_PREDICT="${SANDBOX_PREDICT}:${PORTAGE_GPG_DIR}"