Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Oct 2002 11:10:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Oct 2002 11:08:52 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:1031 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Wed, 9 Oct 2002 11:08:43 -0400 Date: Wed, 9 Oct 2002 08:16:06 -0700 (PDT) From: Linus Torvalds To: "Randy.Dunlap" cc: Brendan J Simon , Roman Zippel , linux-kernel , kbuild-devel Subject: Re: [kbuild-devel] Re: linux kernel conf 0.8 In-Reply-To: Message-ID: 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 Content-Length: 1329 Lines: 32 On Wed, 9 Oct 2002, Randy.Dunlap wrote: > > stick with TCL/TK, like xconfig currently uses ? Too ugly. I actually think QT is a fine choice, I just suspect that it's going to cause political issues. My favourite approach by far is to actually not ship anything graphical with the kernel at all, and just hope that the config language syntax is stable enough that different groups can do their own as external packages. The kernel would ship with just the text-based "reference implementation" (if even that - we could just have a few "supporting packages"). The only thing I personally really care about is the Config language, since that _has_ to ship with the kernel. Linus PS. And while we're talking about the language - I'd actually prefer the syntax "depends on" or "requires" instead of "depends", to make it grammatically more correct. And those help-texts should be separated some way so that they don't blend in quite as badly with the "command section". Maybe something really syntactic like just replacing the "help" keyword with a "---help---" keyword. - 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/