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

Hi,

On 17 Sep 2005 19:16:33 +0200, Krzysztof Halasa <[email protected]> wrote:
> 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

menuconfig is _part_ of kernel configuration system.

Regards,
Michal Piotrowski
-
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: Krzysztof Halasa <[email protected]>

References:
- Why don't we separate menuconfig from the kernel?
  - From: Krzysztof Halasa <[email protected]>

Prev by Date: Re: ppc64: BPA iommu fails to build (BUILD_BUG_ON)
Next by Date: Re: [PATCH] per process I/O statistics for userspace
Previous by thread: Why don't we separate menuconfig from the kernel?
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]