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 7DCD8138663 for ; Thu, 24 Jan 2013 21:30:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4136E21C06E; Thu, 24 Jan 2013 21:30:45 +0000 (UTC) Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 36AFE21C009 for ; Thu, 24 Jan 2013 21:30:43 +0000 (UTC) Received: by mail-ia0-f172.google.com with SMTP id u8so5559234iag.31 for ; Thu, 24 Jan 2013 13:30:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=VFIKN7BOTphxt+3siNnSCjadHiRzH22Nzbf18sv7zow=; b=fp+z1OzeF4xTilBDWRPcuNes2XdDN02HHTf/kcQvAbL8+h332i/S0RCy4KNTTq5/yn x0WpaowihBCjpQIuYWCvTnMUbSR45gcGp1YepeK1a1zfzIndGgYMf3+LCH1TijrZFaB0 WxxQujGRJadbsYV1cfFzKioej0VxuwctftNVfseaoEI8+F1QBg/3KZQIXN1avCPMgk7Y pUaVGYSGcnM8StJktjHi6tTOnUKXkYijsKhALIZq7JlFfbgxQ3y45iLVCCZQDxs3t054 xuN4dIHeQBBULuVVLR6797HVEwEqduVT4quJmMgnhSJI3op0GyjJ3/iGbROMygx6ky4R jVLQ== 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 X-Received: by 10.50.207.67 with SMTP id lu3mr2641807igc.12.1359063043339; Thu, 24 Jan 2013 13:30:43 -0800 (PST) Sender: freemanrich@gmail.com Received: by 10.64.30.231 with HTTP; Thu, 24 Jan 2013 13:30:43 -0800 (PST) In-Reply-To: <510189CE.3020700@orlitzky.com> References: <50FE73F1.6090102@gmail.com> <51017B0A.4060608@gentoo.org> <510183B2.8020603@orlitzky.com> <5101844B.8070005@gentoo.org> <510189CE.3020700@orlitzky.com> Date: Thu, 24 Jan 2013 16:30:43 -0500 X-Google-Sender-Auth: djTCuCAnxIQ8RnjL60regmIxZWw Message-ID: Subject: Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default From: Rich Freeman To: gentoo-dev Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 797587b5-7d8b-470a-9d52-24cbc2798bb2 X-Archives-Hash: a338273b668d1b3fb1ca58b288e59056 On Thu, Jan 24, 2013 at 2:21 PM, Michael Orlitzky wrote: > On 01/24/13 13:58, Ian Stakenvicius wrote: >> >> >> How about, you know what you're doing and are going to build a new >> kernel as soon as the emerge finishes (since the emerge is also >> bringing in a new gentoo-sources)?? >> > > If you're going to upgrade both anyway, you should be upgrading the > kernel first. That way if you lose power or the system crashes, the box > can reboot. The problem is that we're trying to solve a very specific issue (a udev upgrade, which already happened) with a general solution. Whatever we come up with has to be override-able in a way that doesn't then just come back to haunt them. As far as what order you upgrade what in - in the case where I'd be most likely to run into this the system wouldn't be bootable before I upgrade, or after I upgrade. I'd tend to run into this issue when building a new system from a stage3 - just dump a bunch of stuff in @world (including a kernel) and then run an emerge -uDN world followed by building a kernel. Yes, this isn't a typical case, and neither are the 10 billion other cases where config checks break. However, typical users don't run Gentoo to begin with. Everybody has some odd case or another - so we warn people of potential breakage before we break things and let them use the brains they needed to get Gentoo working in the first place. Rich