From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0A8711385F7 for ; Tue, 22 Jan 2013 14:49:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A71DA21C0A8; Tue, 22 Jan 2013 14:49:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9EF7721C05B for ; Tue, 22 Jan 2013 14:49:39 +0000 (UTC) Received: from [192.168.26.5] (ip98-164-195-43.oc.oc.cox.net [98.164.195.43]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id A101433DB09 for ; Tue, 22 Jan 2013 14:49:38 +0000 (UTC) Message-ID: <50FEA6FE.7080001@gentoo.org> Date: Tue, 22 Jan 2013 06:49:34 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default References: <50FE0B5A.3080703@gentoo.org> <50FE0DFC.9030809@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: d8bd27b2-7f2d-46d9-b642-e7be891ea513 X-Archives-Hash: 510c03be47b15ee27ea366e291246c6b On 01/22/2013 01:22 AM, Markos Chandras wrote: > On 22 January 2013 03:56, 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 >> -- >> Thanks, >> Zac >> > > I guess the problem is when you create a binpkg and not when you > install it on the target. Would it be possible to make > this nonfatal if FEATURES contains "binpkg" or -B was passed to > emerge? The closest thing that PMS has defined is the MERGE_TYPE variable, which is supported since EAPI 4. This variable has 3 possible values: source, buildonly, or binary. Ebuilds can detect emerge --buildpkgonly by checking for [[ ${MERGE_TYPE} == buildonly ]]. However, for normal --buildpkg or FEATURES="buildpkg", the MERGE_TYPE is "source". -- Thanks, Zac