Why don't we separate menuconfig from the kernel?

Hi,

A number of packages (e.g., busybox) use some, more or less broken,
version of menuconfig. Would it make sense to move menuconfig to
a separate well-defined package?

Nooo? Why not?
-- 
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Why don't we separate menuconfig from the kernel?
  - From: Jesper Juhl <[email protected]>
- Re: Why don't we separate menuconfig from the kernel?
  - From: Michal Piotrowski <[email protected]>

Prev by Date: Re: 2.6.14-rc1 breaks tg3 on ia64
Next by Date: Re: [Patch] Support UTF-8 scripts
Previous by thread: mmap (2) vs read (2)
Next by thread: Re: Why don't we separate menuconfig from the kernel?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind]