From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: alternative linux configurator prototype v0.2
Date: Mon, 18 Mar 2002 00:38:30 +0100 [thread overview]
Message-ID: <20020317233830.GA2679@werewolf.able.es> (raw)
In-Reply-To: <3C9396F5.7319AB27@linux-m68k.org> <3C94948E.777B5BAF@linux-m68k.org>
In-Reply-To: <3C94948E.777B5BAF@linux-m68k.org>; from zippel@linux-m68k.org on dom, mar 17, 2002 at 14:05:18 +0100
On 2002.03.17 Roman Zippel wrote:
>Hi,
>
>I wrote:
>
>> At http://www.xs4all.nl/~zippel/lc.tar.gz you can find a prototype for a
>> new linux configurator (see the included README for build/use
>> information). It has reached a point, where it's becoming usable and I
>> need some feedback on how/if to continue.
>
After seeing all that many tools for kernel config, I always wanted to ask
this.
There is something (as an 'external' viewer) I never understood.
Why nobody has taken the 'obvious' way ?
- Perl is much more extended that python and better? than sh for CML.
- Perl has perl-Curses (for menuconfig)
- Perl has perl-GTK (for xconfig) (so you geet rid of tcl/tk)
Reasons ?
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Bluebird) for i586
Linux werewolf 2.4.19-pre3-jam3 #1 SMP Fri Mar 15 01:16:08 CET 2002 i686
next prev parent reply other threads:[~2002-03-17 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 19:03 alternative linux configurator prototype Roman Zippel
2002-03-17 13:05 ` alternative linux configurator prototype v0.2 Roman Zippel
2002-03-17 23:38 ` J.A. Magallon [this message]
2002-03-18 0:43 ` Roman Zippel
2002-03-19 14:05 ` Alex Riesen
2002-03-19 19:27 ` Roman Zippel
2002-03-19 20:21 ` christophe barbé
2002-03-20 12:35 ` Roman Zippel
2002-03-20 15:02 ` christophe barbé
2002-03-22 0:53 ` alternative linux configurator specification v0.1 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=20020317233830.GA2679@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.