From: Jes Sorensen <jes@sunsite.dk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Bob Glamm <glamm@mail.ece.umn.edu>, linux-kernel@vger.kernel.org
Subject: Re: Will 2.6 require Python for any configuration ? (CML2)
Date: 23 Aug 2001 21:26:33 +0200 [thread overview]
Message-ID: <d3k7zutw5y.fsf@lxplus051.cern.ch> (raw)
In-Reply-To: <20010822030807.N120@pervalidus> <20010823140555.A1077@newton.bauerschmidt.eu.org> <20010823103620.A6965@kittpeak.ece.umn.edu> <20010823085900.F14302@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: Tom Rini's message of "Thu, 23 Aug 2001 08:59:00 -0700"
>>>>> "Tom" == Tom Rini <trini@kernel.crashing.org> writes:
Tom> On Thu, Aug 23, 2001 at 10:36:20AM -0500, Bob Glamm wrote:
Tom> And the same set of replies. Doing it in !python would be much
Tom> harder than it sounds. But people have stepped up and said
Tom> they'd do it in C. So python is only needed for xconfig. And
Tom> that's just trading tcl for python. The other thing is, the
Tom> python cml2 tools are supposed to eliminate a bunch of other
Tom> tools and remove some of the dependancies.
Most of these tools were written in bash or C ... going the python way
is a major loss.
>> Why isn't ncurses a pain? For the same reason ncurses wasn't a
>> pain when 'make menuconfig' (lxdialog) was introduced (yes, I did
>> many a 'make config'): curses/ncurses was already on just about
>> every system running Linux - it was built into the text editor.
Tom> And many a new system has python.
It still doesn't solve the situation of people building embedded
systems who do only have a bare minimum on their systems. Or people
who are bringing up systems who do not have network/floppy available
and do not want to move their disks between systems constantly in
order to configure their kernels. I have brought this point up
several times to the CML2 developer and every time I received the
utterly useless answer saying I should move my source to another box,
configure it there and move it back to the devel box.
>> It does surprise me that Linus would actually allow this to happen.
>> It's been my impression that he favors a clean, elegant solution.
>> Maybe it's just me, but adding a dependency solely for the sake of
>> building the kernel doesn't strike me as very clean or elegant.
Tom> Because the python solution happened to fix all of the problems.
And introduces new problems that so far haven't been addressed.
The solution seems to be that someone implements CML2 in C, once that
happens we are talking something completely different.
Jes
next prev parent reply other threads:[~2001-08-23 19:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 6:08 Will 2.6 require Python for any configuration ? (CML2) =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier
2001-08-23 12:05 ` Roland Bauerschmidt
2001-08-23 15:36 ` Bob Glamm
2001-08-23 15:55 ` Disconnect
2001-08-23 18:36 ` Daniel Phillips
2001-08-23 18:44 ` Disconnect
2001-08-23 19:01 ` David Weinehall
2001-08-23 19:22 ` Alan Cox
2001-08-23 19:02 ` Roland Bauerschmidt
2001-08-23 19:09 ` Rik van Riel
2001-08-23 19:31 ` Disconnect
2001-08-23 22:52 ` John Alvord
2001-08-24 1:51 ` Keith Owens
2001-08-23 15:55 ` Joshua Schmidlkofer
2001-08-23 15:59 ` Tom Rini
2001-08-23 19:26 ` Jes Sorensen [this message]
2001-08-23 19:32 ` David Weinehall
2001-08-23 19:41 ` Tom Rini
2001-08-23 19:50 ` Tom Rini
2001-08-23 20:02 ` Jes Sorensen
2001-08-23 20:13 ` Tom Rini
2001-08-23 20:43 ` Jes Sorensen
2001-08-23 21:12 ` Tom Rini
2001-08-24 4:59 ` Denis Perchine
2001-08-24 6:35 ` Leonid Mamtchenkov
2001-08-24 7:13 ` Denis Perchine
2001-08-24 15:01 ` Mark Hahn
2001-08-24 13:35 ` Ryan W. Maple
2001-08-25 1:14 ` Michael Peddemors
2001-08-24 17:42 ` David Lang
2001-08-23 16:24 ` Roland Bauerschmidt
2001-08-23 17:57 ` Kurt Roeckx
2001-08-24 8:10 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2001-08-23 20:41 Samium Gromoff
2001-08-23 20:53 ` Tom Rini
2001-08-25 4:11 ` Ben Ford
2001-08-25 14:51 ` Tom Rini
2001-08-23 20:56 Samium Gromoff
2001-08-23 21:14 ` Tom Rini
2001-08-23 21:08 Rick Hohensee
2001-08-23 21:01 ` Tom Rini
2001-08-23 21:12 Samium Gromoff
2001-08-23 21:32 ` Tom Rini
2001-08-23 21:18 Samium Gromoff
2001-08-23 21:34 ` Tom Rini
2001-08-24 12:59 ` Jes Sorensen
2001-08-24 15:37 ` Tom Rini
2001-08-24 15:42 ` Jes Sorensen
2001-08-24 15:50 ` Tom Rini
2001-08-24 16:03 ` Jes Sorensen
2001-08-23 21:39 Samium Gromoff
[not found] <20010823191423.I14302@cpe-24-221-152-185.az.sprintbbd.net>
2001-08-24 3:01 ` Rick Hohensee
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=d3k7zutw5y.fsf@lxplus051.cern.ch \
--to=jes@sunsite.dk \
--cc=glamm@mail.ece.umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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