| 1 |
On Fri, Nov 4, 2011 at 10:18 PM, Robin H. Johnson <robbat2@g.o> wrote: |
| 2 |
> On Fri, Nov 04, 2011 at 04:11:42PM +0100, Fabio Erculiani wrote: |
| 3 |
>> On Fri, Nov 4, 2011 at 3:46 PM, Mike Gilbert <floppym@g.o> wrote: |
| 4 |
>> > |
| 5 |
>> > It is good that we warn users about this when they install the package, |
| 6 |
>> > but I don't think the ebuild should die. |
| 7 |
>> |
| 8 |
>> I've always found ebuilds dying at kernel config checks really annoying. |
| 9 |
>> Checking kernel features at build time (if we die) is broken and |
| 10 |
>> should be banned IMO: |
| 11 |
> You're going off on a tangent. |
| 12 |
> |
| 13 |
> The ONLY time that kernel config checks are fatal is when you're |
| 14 |
> building kernel modules, and the module will fail to compile unless |
| 15 |
> there is a .config and suitable options set. |
| 16 |
|
| 17 |
And that is bad anyway, because it doesn't work as expected when the |
| 18 |
package is merged from tbz2, there are no kernel sources installed and |
| 19 |
multiple kernels are on the same system (and perhaps you are using a |
| 20 |
package manager that properly supports multiple installed kernel |
| 21 |
module packages). |
| 22 |
|
| 23 |
> |
| 24 |
> chromium is using the fatal mode of CONFIG_CHECK wrongly. |
| 25 |
> |
| 26 |
> -- |
| 27 |
> Robin Hugh Johnson |
| 28 |
> Gentoo Linux: Developer, Trustee & Infrastructure Lead |
| 29 |
> E-Mail : robbat2@g.o |
| 30 |
> GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
| 31 |
> |
| 32 |
> |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Fabio Erculiani |
| 38 |
http://lxnay.com |
Archives