From 1ba69403ceb5b3fe7e75e1781b51a072213e6d32 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Fri, 30 Nov 2007 09:03:26 +0000 Subject: 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. (trunk r8761) svn path=/main/branches/2.1.2/; revision=8762 --- bin/ebuild.sh | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'bin/ebuild.sh') diff --git a/bin/ebuild.sh b/bin/ebuild.sh index f8f7377d7..78c423278 100755 --- a/bin/ebuild.sh +++ b/bin/ebuild.sh @@ -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}" -- cgit v1.2.3-1-g7c22