public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "J.A. Magallón" <jamagallon@able.es>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig (qt) -> Gconfig (gtk)
Date: Sun, 3 Nov 2002 03:09:09 +0000	[thread overview]
Message-ID: <20021103030909.A11401@infradead.org> (raw)
In-Reply-To: <1036287009.18289.5.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Sun, Nov 03, 2002 at 01:30:09AM +0000

On Sun, Nov 03, 2002 at 01:30:09AM +0000, Alan Cox wrote:
> On Sun, 2002-11-03 at 00:06, J.A. Magallón wrote:
> > As I see it, the onle thing that should be included in a standard kernel
> > would be something like a kconfig-xaw, that is sure to be on every box that
> > has X, and could be a reference implementation.
> 
> Lots of people no longer include Xaw either nowdays 8)
> 
> Probably the easiest way to do this would be to move the GUI tools out
> of the kernel (or maybe leave the common useful ones) and have make
> guiconfig do
> 
> 	if [ -f /usr/sbin/kernel-gui-config ] ; then
> 		/usr/sbin/kernel-gui-config
> 	elif got_qt() ; then
> 		qt config
> 	elif got_gtk() ; then
> 		gtk_config
> 	else
> 		warnign message
> 		make config
> 	fi

Why does the kernel have to know about that tools at all?  Just put them
into $PATH and let people just call $FOOCONFIG.  This works pretty well
with mconfig on 2.2/2.4..


  reply	other threads:[~2002-11-03  3:02 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 22:21 Kconfig (qt) -> Gconfig (gtk) Romain Lievin
2002-11-02  7:03 ` Nero
2002-11-02 20:36   ` Dr. David Alan Gilbert
2002-11-02 17:00     ` Jon Portnoy
2002-11-02 22:19       ` bert hubert
2002-11-02 19:45     ` Nero
2002-11-02 20:42     ` Xavier Bestel
2002-11-02 21:12       ` David B. Stevens
2002-11-02 21:07     ` Russell King
2002-11-02 22:43       ` Marek Habersack
2002-11-02 22:48         ` Sam Ravnborg
2002-11-02 21:25     ` Dave Jones
2002-11-02 21:59     ` Alan Cox
2002-11-02 21:57       ` Patrick Finnegan
2002-11-02 22:06         ` Russell King
2002-11-02 22:33           ` Roman Zippel
2002-11-02 22:34             ` Russell King
2002-11-03  3:18               ` Gerhard Mack
2002-11-02 22:47             ` Sam Ravnborg
2002-11-02 23:03               ` Roman Zippel
2002-11-02 22:56         ` Alan Cox
2002-11-02 23:07           ` Patrick Finnegan
2002-11-03  4:07           ` Matthew D. Pitts
2002-11-04  4:57           ` Stefan Traby
2002-11-04  6:21             ` Sam Ravnborg
2002-11-02 23:28         ` Dr. David Alan Gilbert
2002-11-02 22:43           ` Nero
2002-11-02 23:59             ` Roman Zippel
2002-11-03  0:06               ` J.A. Magallón
2002-11-02 23:16                 ` Nero
2002-11-03  1:30                 ` Alan Cox
2002-11-03  3:09                   ` Christoph Hellwig [this message]
2002-11-03  9:47                     ` Geert Uytterhoeven
2002-11-03 12:56                       ` Christoph Hellwig
2002-11-03  4:42                   ` Randy.Dunlap
2002-11-03  0:07             ` Patrick Finnegan
2002-11-03  3:53             ` George Staikos
2002-11-03  9:08               ` Nero
2002-11-06  0:45         ` Bill Davidsen
2002-11-06  1:25           ` Mariusz Zielinski
2002-11-03  1:15     ` Rando Christensen
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 13:43 Where's the documentation for Kconfig? Matthew Wilcox
2002-10-31 14:43 ` Roman Zippel
2002-11-01 12:52   ` Russell King
2002-11-01 13:50     ` Roman Zippel
2002-11-01 19:31       ` Russell King
2002-11-01 20:35         ` Roman Zippel
     [not found]           ` <20020625221306.GA439@free.fr>
     [not found]             ` <Pine.LNX.4.44.0211021254420.6949-100000@serv>
2002-11-02 13:20               ` Kconfig (qt) -> Gconfig (gtk+) Romain Lievin
2002-11-02 14:45                 ` Roman Zippel

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=20021103030909.A11401@infradead.org \
    --to=hch@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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