lkml.org 
[lkml]   [2003]   [Jul]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Make menuconfig broken
Date
In article <Pine.LNX.4.44.0307222129070.17797-100000@phoenix.infradead.org>,
James Simmons <jsimmons@infradead.org> wrote:
| > Well there are 2 issues here:
| >
| > 1) How to handle "make oldconfig" on 2.4 config files. Which may not be
| > fixable in a manner that doesn't involve really ugly code.
| >
| > 2) That make menuconfig|xconfig on a clean 2.6 tree results in a kernel
| > that doesn't have console support. This will be something that will
| > come up over and over again in the future, and does not require ugly
| > hacks to fix.
|
| Instead of hacking up a oldconfig why not have the system detect old
| config files and refuse to build it and tell the user to start from
| scratch. I think this is acceptable.

I would say defconfig first, then menuconfig, but whatever. If you can't
do it right, don't do it at all. The problems introduced by almost-right
conversions are often harder to find than starting from default.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:47    [from the cache]
©2003-2011 Jasper Spaans