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

"Martin Fouts" <[email protected]> writes:

> I don't have a patch yet, but I've just spent a bit of time looking at
> how kbuild works, and I believe there is a fairly straightforward way to
> keep kbuild in the kernel tree but make it easy to split it out so that
> someone could use it as a separate tool.

That is obvious and people already are doing that, what I'm thinking of is
moving menuconfig or *config out of the kernel so there is one well-defined
external package.
-- 
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: Ian Campbell <[email protected]>

• References:
  • RE: Why don't we separate menuconfig from the kernel?
    • From: "Martin Fouts" <[email protected]>

• Prev by Date: Re: Why don't we separate menuconfig from the kernel?
• Next by Date: Re: p = kmalloc(sizeof(*p), )
• Previous by thread: Re: 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]