Gentoo Archives: gentoo-dev

From: Michael Orlitzky <michael@××××××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default
Date: Thu, 24 Jan 2013 20:39:57
Message-Id: 51019C17.9000909@orlitzky.com
In Reply to: Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default by "vivo75@gmail.com"
1 On 01/24/13 15:26, vivo75@×××××.com wrote:
2 >> If you're going to upgrade both anyway, you should be upgrading the
3 >> kernel first. That way if you lose power or the system crashes, the box
4 >> can reboot.
5 >>
6 > which can be the exact opposite order if instead you have to _disable_ a
7 > feature in the kernel which would make udev not bootable.
8 > Don't remember exactly what, but it happened in the past when Greg was
9 > still maintainer and an obsolete feature was making udev confused.
10 >
11
12 Suppose, you're on e.g. udev-1, and,
13
14 * udev-2 requires CONFIG_FOO=n
15 * udev-1 will not boot with CONFIG_FOO=y
16
17 Then it doesn't make much sense to die without CONFIG_FOO=n, because it
18 can't possibly exist. So we would warn with either a non-fatal config
19 check or news item. Hopefully we would also execute the person responsible.

Replies

Subject Author
Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default Michael Orlitzky <michael@××××××××.com>