On Fri, Nov 4, 2011 at 10:18 PM, Robin H. Johnson <[email protected]> wrote: > On Fri, Nov 04, 2011 at 04:11:42PM +0100, Fabio Erculiani wrote: >> On Fri, Nov 4, 2011 at 3:46 PM, Mike Gilbert <[email protected]> wrote: >> > >> > It is good that we warn users about this when they install the package, >> > but I don't think the ebuild should die. >> >> I've always found ebuilds dying at kernel config checks really annoying. >> Checking kernel features at build time (if we die) is broken and >> should be banned IMO: > You're going off on a tangent. > > The ONLY time that kernel config checks are fatal is when you're > building kernel modules, and the module will fail to compile unless > there is a .config and suitable options set.
And that is bad anyway, because it doesn't work as expected when the package is merged from tbz2, there are no kernel sources installed and multiple kernels are on the same system (and perhaps you are using a package manager that properly supports multiple installed kernel module packages). > > chromium is using the fatal mode of CONFIG_CHECK wrongly. > > -- > Robin Hugh Johnson > Gentoo Linux: Developer, Trustee & Infrastructure Lead > E-Mail : [email protected] > GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 > > -- Fabio Erculiani http://lxnay.com
