From: Roman Zippel <zippel@linux-m68k.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Brendan J Simon <brendan.simon@bigpond.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] Re: linux kernel conf 0.8
Date: Wed, 9 Oct 2002 17:14:11 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0210091705160.8911-100000@serv> (raw)
In-Reply-To: <20021009144502.GD2954@werewolf.able.es>
Hi,
On Wed, 9 Oct 2002, J.A. Magallon wrote:
> >stick with TCL/TK, like xconfig currently uses ?
> >or is it not sufficient? or just too ugly?
> >
>
> What is linux kernel conf written in ?
> - perl: use perl-gtk (I think there is also a perl-qt)
> - python: use py-gtk...
>
> Use whatever the language gives. I never undestook why use tcl/tk
> on a perl/python config system.
With the exception of the X interface everything is in C, what makes it
difficult to use script languages, one always needs some extra development
package installed. That's the main reason for creating a library backend,
a lot can already be packaged by distributions and only the library needs
to be built from the current kernel.
bye, Roman
next prev parent reply other threads:[~2002-10-09 15:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210081830350.4396-100000@home.transmeta.com>
2002-10-09 12:01 ` Roman Zippel
2002-10-09 13:35 ` Jeff Garzik
2002-10-09 13:55 ` Roman Zippel
2002-10-09 14:07 ` Jeff Garzik
2002-10-09 14:14 ` [kbuild-devel] " Brendan J Simon
2002-10-09 14:28 ` Jeff Garzik
2002-10-09 14:24 ` Brendan J Simon
2002-10-09 14:34 ` Randy.Dunlap
2002-10-09 14:45 ` J.A. Magallon
2002-10-09 15:14 ` Roman Zippel [this message]
2002-10-09 15:16 ` Linus Torvalds
2002-10-09 15:19 ` Randy.Dunlap
2002-10-09 16:29 ` Roman Zippel
2002-10-09 16:40 ` Christoph Hellwig
2002-10-09 18:39 ` Roman Zippel
2002-10-09 18:52 ` Peter Samuelson
2002-10-09 19:28 ` Randy.Dunlap
2002-10-09 19:39 ` Sam Ravnborg
2002-10-09 19:47 ` Randy.Dunlap
2002-10-09 14:55 ` [kbuild-devel] " Roman Zippel
2002-10-09 17:16 ` Sam Ravnborg
2002-10-09 17:37 ` Linus Torvalds
2002-10-09 17:55 ` Sam Ravnborg
2002-10-09 18:47 ` Linus Torvalds
2002-10-09 19:26 ` Sam Ravnborg
2002-10-09 20:41 ` Jeff Garzik
2002-10-09 22:49 ` Roman Zippel
2002-10-10 14:18 ` Jeff Garzik
2002-10-10 17:29 ` Sam Ravnborg
2002-10-10 17:32 ` Jeff Garzik
2002-10-10 17:51 ` Sam Ravnborg
2002-10-09 23:49 ` [kbuild-devel] " Brendan J Simon
2002-10-09 18:35 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0210091705160.8911-100000@serv \
--to=zippel@linux-m68k.org \
--cc=brendan.simon@bigpond.com \
--cc=jamagallon@able.es \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®