From: | Benda Xu <heroxbd@g.o> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | [gentoo-dev] Re: RFC: toolchain.eclass prefix support | ||
Date: | Sun, 08 Jan 2017 05:01:55 | ||
Message-Id: | 87lgumywko.fsf_-_@gentoo.org | ||
In Reply to: | Re: [gentoo-dev] RFC: toolchain.eclass prefix support by Mike Gilbert |
1 | Mike Gilbert <floppym@g.o> writes: |
2 | |
3 | > Regarding the PATH/gcc-config change, I'm thinking it would make more |
4 | > sense to drop the env -i command than to add to he list of special |
5 | > variables we pass through to it. |
6 | |
7 | All the env -i has been introduced in this commit by vapier in 2005: |
8 | |
9 | https://gitweb.gentoo.org/repo/gentoo/historical.git/commit/?id=a8a64d1886cc5c9f975353b97237f2900a3ee88c |
10 | |
11 | "clean up/simplify the gcc-config and fix_libtool_files logic". The |
12 | reasonale was "clean-up". |
13 | |
14 | |
15 | "ROOT=${ROOT}" was added in 2007 by vapier, |
16 | |
17 | https://gitweb.gentoo.org/repo/gentoo/historical.git/commit/?id=7d9f89700a2ee50674c0d871ec6d21b468ac6206 |
18 | |
19 | "cleanup gcc-config logic so that it doesnt matter what the ROOT value |
20 | is". The reasonale was "cleanup gcc-config logic" |
21 | |
22 | |
23 | So, from the two historical commits, it is safe to drop env -i without |
24 | breaking anything sacred. |
25 | |
26 | Benda |