| 1 |
On Mon, Mar 20, 2017 at 1:01 PM, Alexis Ballier <aballier@g.o> wrote: |
| 2 |
> I just tried and with portage 2.3.5, FILESDIR is unset/empty in global |
| 3 |
> scope here. At least an 'ewarn "${FILESDIR} blah"' outputs only ' blah'. |
| 4 |
|
| 5 |
I cannot reproduce this behavior. |
| 6 |
|
| 7 |
% emerge --version |
| 8 |
Portage 2.3.5_p2 (python 3.5.3-final-0, |
| 9 |
default/linux/amd64/13.0/desktop/plasma/systemd, gcc-5.4.0, |
| 10 |
glibc-2.24-r1, 4.9.14 x86_64) |
| 11 |
|
| 12 |
% cat foo-0.ebuild |
| 13 |
EAPI=6 |
| 14 |
SLOT=0 |
| 15 |
KEYWORDS="amd64" |
| 16 |
einfo "global: FILESDIR=${FILESDIR}" |
| 17 |
pkg_setup() { |
| 18 |
einfo "setup: FILESDIR=${FILESDIR}" |
| 19 |
} |
| 20 |
src_unpack() { |
| 21 |
einfo "unpack: FILESDIR=${FILESDIR}" |
| 22 |
} |
| 23 |
|
| 24 |
% sudo emerge -1BO -j1 app-misc/foo |
| 25 |
|
| 26 |
>>> Verifying ebuild manifests |
| 27 |
|
| 28 |
>>> Emerging (1 of 1) app-misc/foo-0::local |
| 29 |
* global: FILESDIR=/home/floppym/repos/local/app-misc/foo/files |
| 30 |
* setup: FILESDIR=/home/floppym/repos/local/app-misc/foo/files |
| 31 |
>>> Unpacking source... |
| 32 |
* unpack: FILESDIR=/home/floppym/repos/local/app-misc/foo/files |
| 33 |
>>> Source unpacked in /x/portage/app-misc/foo-0/work |
Archives