Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default
Date: Sun, 27 Jan 2013 01:07:01
Message-Id: CAGfcS_=k7sQ=9Jt3c7MKbdJZ9njpWjA7GN_u=6pYP9M4p0fJJw@mail.gmail.com
In Reply to: Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default by Peter Stuge
1 On Sat, Jan 26, 2013 at 7:31 PM, Peter Stuge <peter@×××××.se> wrote:
2 > Rich Freeman wrote:
3 >> having a standardized kernel with a few flags probably isn't a bad idea.
4 >
5 > That doesn't scale at all. Suggest instead take a .config as input to
6 > the emerge, maybe something like savedconfig for busybox, and add
7 > shortcuts for common options.
8 >
9 > That way, the same mechanism can be used for arbitrarily complex
10 > configurations too.
11
12 The intent would be to have all non-mutually-incompatible options
13 enabled as modules and an accompanying initramfs. That's what every
14 single other distro does - it works reasonably well. USE flags might
15 be used for any odd situations that can't be covered in this way
16 (though I can't think of any offhand - odd situations are probably
17 handled best with a manual build).
18
19 If you're just going to feed it a .config file then you might as well
20 use genkernel - the idea is to be bulletproof. Just emerge the
21 package and run grub-install and you have a bootable system.
22
23 Rich