/etc/make.globals contains: /etc/make.globals:#PORTAGE_TMPDIR=${ROOT}/var/tmp /etc/make.globals:PORTAGE_TMPDIR=/var/tmp /etc/make.globals:BUILD_PREFIX=${PORTAGE_TMPDIR}/portage /etc/make.globals:PKG_TMPDIR=${PORTAGE_TMPDIR}/portage-pkg /etc/make.conf contains: /etc/make.conf:PORTAGE_TMPDIR=/usr/local/src /etc/make.conf:PKG_TMPDIR=${PORTAGE_TMPDIR}/portage-pkg emerge output: Calculating dependencies >>> Unpacking source... >>> Unpacking gnome-core-1.4.1.tar.bz2 patching file configure.in Working directory: /var/tmp/portage/gnome-core-1.4.1/work/gnome-core-1.4.1... Applying libtool-relink.patch... Applying libtool-tmp.patch... Applying libtool-portage.patch... The PORTAGE_TMPDIR is ignored, directories in /var/tmp are created and file system is filled up. My work around is a symlink to /usr/local/src/portage, but I didn't have this problem before portage-2.07. set|grep TMP doesn't give output. I can reproduce this issue. Thank you, Wilbert van Bakel
Fixed in Portage 2.0.9