Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-08-06 Thread Kent Fredric
On Sat, 3 Aug 2019 00:07:13 +0100 James Le Cuirot wrote: > Any better? I think I would be personally aided by a description of what sort of environment is expecting the various values, eg: I know if I build for a target that I'll eventually have to "chroot" to get into, paths that get "made con

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-08-02 Thread James Le Cuirot
On Thu, 1 Aug 2019 16:27:22 +0200 Alexis Ballier wrote: > > > What I am trying to say (somewhat unsuccessfully!) is that the value > > of (E)SYSROOT only changes how the package is built, not what the > > resulting package looks like. It's where all the headers and libraries > > are sourced from a

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-08-01 Thread Alexis Ballier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 31 Jul 2019 21:40:19 +0100 James Le Cuirot wrote: > On Wed, 31 Jul 2019 15:51:58 +0200 > Alexis Ballier wrote: > > > On Tue, 30 Jul 2019 23:26:27 +0100 > > James Le Cuirot wrote: > > > > > > Admittedly without a full understanding of th

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-07-31 Thread James Le Cuirot
On Wed, 31 Jul 2019 21:40:19 +0100 James Le Cuirot wrote: > So why does ROOT affect it? Normally you install the packages for > BDEPEND, DEPEND, and RDEPEND to the same location. If BDEPEND and > RDEPEND are installed to different locations (ROOT!=/) then DEPEND will > almost always be installed

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-07-31 Thread James Le Cuirot
On Wed, 31 Jul 2019 15:51:58 +0200 Alexis Ballier wrote: > On Tue, 30 Jul 2019 23:26:27 +0100 > James Le Cuirot wrote: > > > > Admittedly without a full understanding of the problem, but this > > > looks wrong to me: SYSROOT, EPREFIX and BROOT are only relevant in > > > build phases (src_*); (E

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-07-31 Thread Alexis Ballier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 30 Jul 2019 23:26:27 +0100 James Le Cuirot wrote: > > Admittedly without a full understanding of the problem, but this > > looks wrong to me: SYSROOT, EPREFIX and BROOT are only relevant in > > build phases (src_*); (EPREFIX is a little spe

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-07-30 Thread James Le Cuirot
On Mon, 29 Jul 2019 14:05:10 +0200 Alexis Ballier wrote: > There seems to be unneeded whitespace only changes here that make the > diff less readable Sorry about that. I've only changed one cell in that table. > Admittedly without a full understanding of the problem, but this looks > wrong to m

Re: [gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-07-29 Thread Alexis Ballier
On Sun, 28 Jul 2019 22:37:35 +0100 James Le Cuirot wrote: [...] > -& \t{BDEPEND} & > \t{DEPEND} & \t{RDEPEND}, \t{PDEPEND} \\ > +& \t{BDEPEND} & > \t{DEPEND}& \t{RDEPEND}, \t{PDEPEND} \\ > \mid

[gentoo-dev] [PMS] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable

2019-07-28 Thread James Le Cuirot
It was originally envisaged (but not stated in PMS) that SYSROOT would only ever need to equal / or ROOT as a distinct SYSROOT would have no benefit. A check was added to Portage to ensure this held. Myself, the ChromiumOS team, and others have since been caught out by this check when trying to boo