Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default
Date: Tue, 22 Jan 2013 04:14:26
Message-Id: 50FE1214.8010202@gentoo.org
In Reply to: Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default by "Rick \\\"Zero_Chaos\\\" Farina"
1 On 01/21/2013 08:10 PM, Rick "Zero_Chaos" Farina wrote:
2 > On 01/21/2013 10:56 PM, Zac Medico wrote:
3 >> On 01/21/2013 07:45 PM, Mike Gilbert wrote:
4 >>> My suspicion is that portage's environment save/restore process will
5 >>> overwrite any setting I attempt to make on the destination host.
6 >
7 >> If necessary, you can use /etc/portage/bashrc to override
8 >> CONFIG_CHECK_FATAL for binary packages. Something like this would work:
9 >
10 >> [[ ${EMERGE_FROM} == binary ]] && CONFIG_CHECK_FATAL=0
11 >
12 >
13 > does this means I need to start adding "export CONFIG_CHECK_FATAL=0" to
14 > my catalystrc?
15
16 I guess so, if you don't want those fatal config checks to kill your
17 catalyst builds.
18 --
19 Thanks,
20 Zac