Gentoo Archives: gentoo-dev

From: Kent Fredric <kentnl@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable
Date: Tue, 06 Aug 2019 09:52:41
Message-Id: 20190806215225.176c93c3@katipo2.lan
In Reply to: Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable by James Le Cuirot
1 On Sat, 3 Aug 2019 00:07:13 +0100
2 James Le Cuirot <chewi@g.o> wrote:
3
4 > Any better?
5
6 I think I would be personally aided by a description of what sort of
7 environment is expecting the various values, eg:
8
9 I know if I build for a target that I'll eventually have to "chroot" to
10 get into, paths that get "made concrete" in the final image need to be
11 from the perspective of inside that chroot, or they won't work, while
12 paths that pertain to the build process need to be relative to the
13 container of said chroot, or they won't know the absolute location to
14 look at for its dependencies.
15
16 All this talk of "prefix" with differing meanings just confuses me. :/