Messages in this thread | | | Subject | Re: Why don't we separate menuconfig from the kernel? | From | Krzysztof Halasa <> | Date | 18 Sep 2005 12:36:03 +0200 |
| |
"Martin Fouts" <Martin.Fouts@palmsource.com> 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 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/
| |