On Wed, 9 Oct 2002, Peter Samuelson wrote:
| [Roman Zippel]
| > The problem is that the config syntax will continue to evolve and
| > currently I prefer to keep the library close to the matching config
| > files.
| > I think I can keep the basic structure constant, but new options will be
| > added, so IMO it's more likely that a front end works with a newer
| > library than that a library can understand a newer syntax.
|
| Besides which, I think it is ridiculous that one would have to download
| and install a "kernel configurator" just to build a kernel. Current
| minimum requirements for compiling the thing are gcc, binutils and GNU
| make. The kernel can't very well ship a copy of any of those, because
| (a) they're huge and (b) they're useful for many things other than
| building kernels. Roman's library is neither.
Well, we all find some things more ridiculous than others, but...
The kernel would still have the text-mode configurator.
This only applies to the GUI kernel config.
So you wouldn't have to download the kernel config unless you just
wanted that oh-so-pretty GUI to config it.
[rhetorical question:]
So should it be shipped with a full Qt development environment, e.g.?
| (And no, "modutils" isn't a counterexample - you can build, install and
| run a kernel without it.)
-- ~Randy "In general, avoiding problems is better than solving them." -- from "#ifdef Considered Harmful", Spencer & Collyer, USENIX 1992.- 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/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:33 EST