Archives
Archives
| 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 03:57:11 | ||
| Message-Id: | 50FE0DFC.9030809@gentoo.org | ||
| In Reply to: | Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default by Mike Gilbert |
||
| 1 | On 01/21/2013 07:45 PM, Mike Gilbert wrote: |
| 2 | > My suspicion is that portage's environment save/restore process will |
| 3 | > overwrite any setting I attempt to make on the destination host. |
| 4 | |
| 5 | If necessary, you can use /etc/portage/bashrc to override |
| 6 | CONFIG_CHECK_FATAL for binary packages. Something like this would work: |
| 7 | |
| 8 | [[ ${EMERGE_FROM} == binary ]] && CONFIG_CHECK_FATAL=0 |
| 9 | -- |
| 10 | Thanks, |
| 11 | Zac |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default | "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o> |
| Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default | Markos Chandras <hwoarang@g.o> |