public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default
Date: Mon, 21 Jan 2013 23:10:49 -0500	[thread overview]
Message-ID: <50FE1149.9040409@gentoo.org> (raw)
In-Reply-To: <50FE0DFC.9030809@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/21/2013 10:56 PM, Zac Medico wrote:
> On 01/21/2013 07:45 PM, Mike Gilbert wrote:
>> My suspicion is that portage's environment save/restore process will
>> overwrite any setting I attempt to make on the destination host.
> 
> If necessary, you can use /etc/portage/bashrc to override
> CONFIG_CHECK_FATAL for binary packages. Something like this would work:
> 
>   [[ ${EMERGE_FROM} == binary ]] && CONFIG_CHECK_FATAL=0
> 

does this means I need to start adding "export CONFIG_CHECK_FATAL=0" to
my catalystrc?

- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJQ/hFJAAoJEKXdFCfdEflK53UP/3Ngz3yBmkPz6E7sBZhjnJiW
CVaRlXvXs3sSn9zWdAxxVn1Z2z3RP387eb7jEXOoUAyIezwVfBLZIfPXUK8KN8rD
LRSntTv3E1AUpE+N0GlxRGVlKYnDf3g+EAi0M6iEjtcVBxsCNiH+UcmwHvPFp/oN
R4n79qD3jWEMMnm708RqkwKKu+/F4wfpUQe66UhAwd4yFDkndl/lwrtwmgztMjtF
W6V6Z1ZkWg0r0rRTxhuAYwMcYFKunfSzNCnaD72z0d184fwxcSw2N697vAPCXiLp
MbjCENLME3+dk088YvjNoZCCcga+9omsIKDG/gkgTJib4Ibrc028Ut0G1Oyxrx+R
6LzES1GRshlx0W9N+b+CmChffWfaGENXx2sSM5W6yD6eJtxGPw736JxGMQcpSltz
G+z+tLwDbx1rvHDBeAWzSU0k+W6Yx/QJ4L5D1LNaA/S3pEXwU6aK2ipoRpiNrJfC
aRWyJx1KGLF+vhrN70SiFASJyotmQwoFipgHjm5QbBiHn8sK0cq3gf9wb3nLRNoD
Ym7u9plg85y/W1Gme09vqlptMzwymIrCmXQHuBeqwILJ+lsVQBa1rL/0fnMyDftX
GLT35hIWM7OVUufuiKB6xiOLH0h/P9w45wUZBiPzldphd5wYr3TMkZFv4C8Qgc1/
1/h2B65Lw5wfF5SEuVo7
=oVpV
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-01-22  4:09 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  3:38 [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default Robin H. Johnson
2013-01-22  3:45 ` Mike Gilbert
2013-01-22  3:56   ` Zac Medico
2013-01-22  4:10     ` Rick "Zero_Chaos" Farina [this message]
2013-01-22  4:14       ` Zac Medico
2013-01-22  9:22     ` Markos Chandras
2013-01-22 14:49       ` Zac Medico
2013-01-22  4:23 ` Mike Gilbert
2013-01-22  6:22   ` Sergey Popov
2013-01-22  6:44     ` [gentoo-dev] " Duncan
2013-01-22 14:51     ` [gentoo-dev] " Zac Medico
2013-01-22 18:40       ` Robin H. Johnson
2013-01-23 12:32         ` Fabio Erculiani
2013-01-23 12:50           ` Rich Freeman
2013-01-23 21:27             ` Fabio Erculiani
2013-01-23 23:17               ` Francesco Riosa
2013-01-24  1:10           ` Robin H. Johnson
2013-01-24 19:46             ` Fabio Erculiani
2013-01-22 11:11 ` vivo75
2013-01-22 11:56   ` Rich Freeman
2013-01-24 17:04     ` Dustin C. Hatch
2013-01-24 17:49     ` [gentoo-dev] " Duncan
2013-01-24 18:09       ` Rich Freeman
2013-01-24 18:18         ` Ian Stakenvicius
2013-01-24 18:24           ` Dustin C. Hatch
2013-01-24 18:25           ` Rich Freeman
2013-01-24 18:55             ` Michael Orlitzky
2013-01-24 18:58               ` Ian Stakenvicius
2013-01-24 19:05                 ` Rich Freeman
2013-01-24 19:21                 ` Michael Orlitzky
2013-01-24 20:26                   ` vivo75
2013-01-24 20:39                     ` Michael Orlitzky
2013-01-24 20:45                       ` Michael Orlitzky
2013-01-25  0:29                         ` vivo75
2013-01-25  0:37                           ` Michael Orlitzky
2013-01-24 21:30                   ` Rich Freeman
2013-01-26 10:34                     ` Fabio Erculiani
2013-01-26 22:25                       ` Duncan
2013-01-26 22:30                         ` Fabio Erculiani
2013-01-26 22:54                           ` Rich Freeman
2013-01-27  0:31                             ` Peter Stuge
2013-01-27  1:06                               ` Rich Freeman
2013-01-25  1:39               ` Duncan
2013-01-25  1:53                 ` Robin H. Johnson
2013-01-25  2:22                 ` Michael Orlitzky
2013-01-25  3:12                   ` Rich Freeman
2013-01-25  3:27                     ` Michael Orlitzky
2013-01-25  6:15                   ` Duncan
2013-01-25 18:24 ` Nuno J. Silva
2013-01-25 18:47   ` Rich Freeman
2013-01-25 19:19     ` Christopher Head
2013-01-25 19:26       ` Rich Freeman
2013-01-25 19:47     ` Nuno J. Silva
2013-01-25 19:57       ` Rich Freeman
2013-01-25 20:06         ` Nuno J. Silva
2013-01-25 20:31           ` Rich Freeman
2013-01-26  1:51           ` Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50FE1149.9040409@gentoo.org \
    --to=zerochaos@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox