From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux kernel config converter
Date: Thu, 21 Feb 2002 07:32:17 -0500 [thread overview]
Message-ID: <3C74E8D1.D74BAD5@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0202211312510.2318-100000@serv>
Roman Zippel wrote:
> On Thu, 21 Feb 2002, Jeff Garzik wrote:
> > FWIW a much better transition path is very close to what your tool does,
> > and is a suggestion made by mec (kbuild maintainer) near the end of the
> > recent flamewar: convert config.in files one at a time, like we did the
> > old makefiles.
>
> That's possible, as soon as the menu information is added, both formats
> contain the same information, so a program with two parsers can handle
> both simultaneously.
yep
> > That would imply a rewrite of make [old]config, and an updating of make
> > menu|xconfig, to handle the new format...
>
> I think we should just dump the old tools and implement a single config
> library, which exports an interface to access the config information.
I do not think we can -avoid- dumping scripts/Configure[1], replacing
the existing tools. In that respect I agree with Eric and the others.
So your proposition makes sense. But the configuration language can and
should be migrated, IMO.
Jeff
[1] Sure you could code a replacement parser in bash shell script. But
that's just wanking, like a Georgia Tech professor of mine: he
implemented a visual Towers of Hanoi solver in vi macros. We all
thought it was cool but ultimately CS wanking of no real value :)
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
next prev parent reply other threads:[~2002-02-21 12:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 10:48 linux kernel config converter Roman Zippel
2002-02-21 11:40 ` Jeff Garzik
2002-02-21 12:21 ` Roman Zippel
2002-02-21 12:32 ` Jeff Garzik [this message]
2002-02-21 12:54 ` Erik Andersen
2002-02-21 13:21 ` Jeff Garzik
2002-02-21 14:28 ` David Lang
2002-02-21 14:36 ` Jeff Garzik
2002-02-21 14:40 ` David Lang
2002-02-21 15:05 ` Jeff Garzik
2002-02-21 15:41 ` Jason Lunz
2002-02-21 15:54 ` Jeff Garzik
2002-02-21 15:18 ` Alan Cox
2002-02-21 15:08 ` Jeff Garzik
2002-02-21 15:22 ` Gerd Knorr
2002-02-21 15:33 ` Roman Zippel
2002-02-21 18:53 ` Andreas Dilger
[not found] <fa.gq2s5iv.1s4in@ifi.uio.no>
2002-02-21 13:28 ` Giacomo Catenazzi
2002-02-21 14:11 ` Roman Zippel
2002-02-21 14:32 ` Giacomo Catenazzi
2002-02-21 15:19 ` Roman Zippel
[not found] <fa.fsgrt4v.1bngh9t@ifi.uio.no>
[not found] ` <fa.hp69onv.i7qtq3@ifi.uio.no>
2002-02-21 14:06 ` Giacomo Catenazzi
2002-02-21 14:26 ` Jeff Garzik
2002-02-21 14:39 ` Giacomo Catenazzi
2002-02-21 15:11 ` Jeff Garzik
2002-02-21 16:00 ` Randy.Dunlap
[not found] ` <fa.lqt3hav.190o1i9@ifi.uio.no>
2002-02-21 14:50 ` Giacomo Catenazzi
2002-02-21 14:56 ` David Lang
2002-02-21 15:05 ` Giacomo Catenazzi
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=3C74E8D1.D74BAD5@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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