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 5493E1385B2 for ; Tue, 22 Jan 2013 03:45:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 09811E062C; Tue, 22 Jan 2013 03:45:35 +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 27591E060D for ; Tue, 22 Jan 2013 03:45:34 +0000 (UTC) Received: from [192.168.1.204] (76-230-137-203.lightspeed.livnmi.sbcglobal.net [76.230.137.203]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 2A45233DB34 for ; Tue, 22 Jan 2013 03:45:33 +0000 (UTC) Message-ID: <50FE0B5A.3080703@gentoo.org> Date: Mon, 21 Jan 2013 22:45:30 -0500 From: Mike Gilbert User-Agent: Mozilla/5.0 (X11; Linux 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: In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2TUMVJKDNBURUSGIKQLCB" X-Archives-Salt: 8183ba32-8adb-4a84-b685-eef00946c030 X-Archives-Hash: bc9ddfb8d443018bb7eac8a921745baa This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2TUMVJKDNBURUSGIKQLCB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 01/21/2013 10:38 PM, Robin H. Johnson wrote: > I'm raising this patch because of the recent spate of bugs with the > latest udev that now fails to boot your system if CONFIG_DEVTMPFS is > not available in your kernel. >=20 > Bugs: 408947, 409393, 437320, 453074=09 >=20 > CONFIG_CHECK has not been fatal for some years now, because there turne= d > out to be some cases where it cannot detect what the system really has > [1], or what is returned is wrong [2]. >=20 > However, while this is has been superb in helping those corner-cases, > the fallout is that users frequently ignore the non-fatal warnings that= > a configuration option is needed to run a binary later, and end up with= > weird breakage. >=20 > This patch introduces a new option, CONFIG_CHECK_FATAL, defaulting to > enabled, that explicitly causes a die if: > - CONFIG_CHECK cannot be performed successfully. > - Any CONFIG_CHECK options fail. >=20 > For the aforementioned corner cases, those environments are used to > customizing their make.conf heavily, and they should add: > CONFIG_CHECK_FATAL=3D0 >=20 > This patch does NOT change the handling of ~/tilde in CONFIG_CHECK > - options that are required at compile-time MUST NOT use ~/tilde. > - options that are only required at run-time MUST include the ~/tilde. >=20 > Footnotes: > 1. If you are using a VM environment, where the kernel is provided > outside of your VM, and you don't have kernel sources, or > /proc/config.gz, you CANNOT detect what options the kernel is > configured with. > 2. Building stages for example. You may have /proc bind-mounted from th= e > host system, but it does not reflect the environment you are buildin= g > for. >=20 How does this variable interact with binpkgs? For example, if I build a package on a system that does not have CONFIG_CHECK_FATAL=3D0, what happens if I try to install it on a system that does not have a usable kernel config? My suspicion is that portage's environment save/restore process will overwrite any setting I attempt to make on the destination host. ------enig2TUMVJKDNBURUSGIKQLCB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlD+C1oACgkQC77qH+pIQ6T1YwD/df2QE7CiCGDLGEjp+Lzt/fLb HJpYqkwTLQui1mxPuoQBAKOdxuk1XU3lGfiS6L3ThXIrOThpiBUn0kogU+ubznD/ =kDsL -----END PGP SIGNATURE----- ------enig2TUMVJKDNBURUSGIKQLCB--