From: "J.A. Magallón" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: [RFC] Kernel GUI config
Date: Sun, 3 Nov 2002 00:14:35 +0100 [thread overview]
Message-ID: <20021102231435.GA2384@werewolf.able.es> (raw)
Hi all...
I have readl all the comments about qconfig, gconfig, etc..., and I wanto to
comment about an idea that perhaps can make everybody happy...
I don't like qt. As many others. Others do not like GTK. QT requires a C++
compiler to configure the kernel. Everybody agrees on putting the gui config
tool outside the tree. So...
- Make a new target called 'guiconfig'. This is neutral, and just should call
an utility called for example kconfig-gui.
- People can implement many different front ends and call them things like
kconfig-qt, kconfig-gtk, kconfig-xaw, etc... The user can configure its
own prefs with an alias or with 'alternatives' as some distros do. None
of this utilities should be included in the tree. Put another dir in
ftp.kernel.org.
To reduce implementation efforts (and bug chasing), as someone said, you
can take all the current parts toolkit-independent (parsers, etc.) from
qconf and split them in a library.
Other possibility is to let parsers in the kernel and generate some kind
of XML file the utilities should read (do not know how hard would be to put
dependencies on an XML file...).
This way even 'menuconfig' could be split as a separate package.
But please, don't force people to use one toolkit.
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-rc1-jam0 (gcc 3.2 (Mandrake Linux 9.0 3.2-2mdk))
next reply other threads:[~2002-11-02 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 23:14 J.A. Magallón [this message]
2002-11-02 23:19 ` J.A. Magallón
2002-11-02 23:27 ` Roman Zippel
2002-11-02 23:29 ` Sam Ravnborg
2002-11-03 3:32 ` Christoph Hellwig
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=20021102231435.GA2384@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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®