| 1 |
On Wed, Sep 21, 2005 at 10:22:08AM -0400, Chris Gianelloni wrote: |
| 2 |
> I see absolutely no problem with that, so long as it is a warning. |
| 3 |
> |
| 4 |
> I mean, you can make it beep, pause, display in flashing red lights and |
| 5 |
> email root@localhost about it for all I care, but it shouldn't *die* on |
| 6 |
> something that isn't a requirement. |
| 7 |
|
| 8 |
I think we all agree by now that we need a way to warn about missing |
| 9 |
CONFIG_ options in addition to the current implementation. Now we just |
| 10 |
need someone to implement it, and have the affected ebuilds changed |
| 11 |
accordingly. |
| 12 |
|
| 13 |
What about the other issue which was brought up? Ebuilds enheriting |
| 14 |
linux-info.eclass requires a configured kernel source? Personally, I |
| 15 |
don't see anything wrong with that, if the above solution is |
| 16 |
implemented (non-fatal checks remain non-fatal). Releng, |
| 17 |
cross-compilers - what are your thoughts on this? |
| 18 |
|
| 19 |
Regards, |
| 20 |
Brix |
| 21 |
-- |
| 22 |
Henrik Brix Andersen <brix@g.o> |
| 23 |
Gentoo Metadistribution | Mobile computing herd |
Archives