From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272133AbTGYOwq (ORCPT ); Fri, 25 Jul 2003 10:52:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272132AbTGYOwq (ORCPT ); Fri, 25 Jul 2003 10:52:46 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:42510 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S272133AbTGYOwp (ORCPT ); Fri, 25 Jul 2003 10:52:45 -0400 Date: Fri, 25 Jul 2003 17:07:46 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@serv To: John Bradford cc: ecki-lkm@lina.inka.de, , , Subject: RE: why the current kernel config menu layout is a mess In-Reply-To: <200307251458.h6PEwAMD001065@81-2-122-30.bradfords.org.uk> Message-ID: References: <200307251458.h6PEwAMD001065@81-2-122-30.bradfords.org.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Fri, 25 Jul 2003, John Bradford wrote: > Maybe a completely new, out of kernel tree configurator would be worth > thinking about, leaving the in-kernel configurator as a legacy option. > I know the config system underwent a major overhaul during 2.5, but I > think we could go even further. Maybe you should look first at something before you throw it away? Kconfig is already modular, the Kconfig parser is a library, which you can easily connect to your favourite script language and then you can do with the Kconfig data whatever you want. bye, Roman