Re: Why don't we separate menuconfig from the kernel?

[Krzysztof Halasa <khc@pm.waw.pl>]

Jesper Juhl <jesper.juhl@gmail.com> writes:

> What exactely is it you want to make a sepperate package?

Just the menuconfig (mconf) at first. OTOH it might make sense to
move them all.

> menuconfig is just a little bit of the kbuild system which also
> includes xconfig, config, gconfig, oldconfig, etc.  menuconfig is just
> a dialog based frontend to the kbuild system which consists of
> configuration options, help texts, dependency info etc.

Sure, that's what I mean. It's used for configuring the kernel, but
other packages use it (well, some version) too. Example: busybox.

There is no much point in keeping more than one copy. They are
completely independent of the kernel, all the kernel wants is to pass
them some Kconfig file and expect data in .config. (oldconfig uses
.config.old).

There is a question about config language and possible future changes.
Not a serious problem IMHO.

> I don't think it makes much sense to split the parts of kbuild that
> make up menuconfig out into a standalone thing. kbuild (and thus
> menuconfig) has little use outside the kernel.

It's not exactly the case.
-- 
Krzysztof Halasa