On Mon, Mar 20, 2017 at 1:01 PM, Alexis Ballier <aball...@gentoo.org> wrote: > I just tried and with portage 2.3.5, FILESDIR is unset/empty in global > scope here. At least an 'ewarn "${FILESDIR} blah"' outputs only ' blah'.
I cannot reproduce this behavior. % emerge --version Portage 2.3.5_p2 (python 3.5.3-final-0, default/linux/amd64/13.0/desktop/plasma/systemd, gcc-5.4.0, glibc-2.24-r1, 4.9.14 x86_64) % cat foo-0.ebuild EAPI=6 SLOT=0 KEYWORDS="amd64" einfo "global: FILESDIR=${FILESDIR}" pkg_setup() { einfo "setup: FILESDIR=${FILESDIR}" } src_unpack() { einfo "unpack: FILESDIR=${FILESDIR}" } % sudo emerge -1BO -j1 app-misc/foo >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-misc/foo-0::local * global: FILESDIR=/home/floppym/repos/local/app-misc/foo/files * setup: FILESDIR=/home/floppym/repos/local/app-misc/foo/files >>> Unpacking source... * unpack: FILESDIR=/home/floppym/repos/local/app-misc/foo/files >>> Source unpacked in /x/portage/app-misc/foo-0/work