Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Oct 2002 14:47:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Oct 2002 14:47:45 -0400 Received: from surf.cadcamlab.org ([156.26.20.182]:44673 "EHLO surf.cadcamlab.org") by vger.kernel.org with ESMTP id ; Wed, 9 Oct 2002 14:47:43 -0400 Date: Wed, 9 Oct 2002 13:52:03 -0500 To: Roman Zippel Cc: linux-kernel , kbuild-devel Subject: Re: linux kernel conf 0.8 Message-ID: <20021009185203.GK4182@cadcamlab.org> References: <20021009174038.A960@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i From: Peter Samuelson Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1116 Lines: 25 [Roman Zippel] > The problem is that the config syntax will continue to evolve and > currently I prefer to keep the library close to the matching config > files. > I think I can keep the basic structure constant, but new options will be > added, so IMO it's more likely that a front end works with a newer > library than that a library can understand a newer syntax. Besides which, I think it is ridiculous that one would have to download and install a "kernel configurator" just to build a kernel. Current minimum requirements for compiling the thing are gcc, binutils and GNU make. The kernel can't very well ship a copy of any of those, because (a) they're huge and (b) they're useful for many things other than building kernels. Roman's library is neither. (And no, "modutils" isn't a counterexample - you can build, install and run a kernel without it.) Peter - 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/