From: Joshua Schmidlkofer <menion@srci.iwpsd.org>
To: Bob Glamm <glamm@mail.ece.umn.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Will 2.6 require Python for any configuration ? (CML2)
Date: Thu, 23 Aug 2001 09:55:46 -0600 [thread overview]
Message-ID: <01082309554604.03507@widmers.oce.srci.oce.int> (raw)
In-Reply-To: <20010822030807.N120@pervalidus> <20010823140555.A1077@newton.bauerschmidt.eu.org> <20010823103620.A6965@kittpeak.ece.umn.edu>
In-Reply-To: <20010823103620.A6965@kittpeak.ece.umn.edu>
> 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.
>
IMHO that is a highly suspect view. Kernel building is already a hideously
complicated problem [At least it seems so to me]. I am certainly in favor
using a more intelligent and capable scripting lang to add capability and
reduce some of the dependancy & symbol issues. If all we are doing is adding
a different front end, it's not of much point, but some genuises here have
streched make + shell to about as far as one can. So if that can be done
with make, someone surley can replace all that with Python. [However, maybe
I have missed the scope of the inclusion of python]
Also, I would like to point out that while Python does have a 'flavor of
the month' look for some people, it is a useable stable solution. Who
knows what my supercede it tomorrow, but as a whole it's maturing, and I
personally use it a TON. Plus it has a powerful library.
Side note:
It took about 10 days for the last kernel compile I did on my 386sx 16
[whopping 32 megs of ram thought =] [that was a while ago].. I suspect that
with python it wouldn't actually take much longer. Besides, I compile
kernels for it on something else.
next prev parent reply other threads:[~2001-08-23 15:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 6:08 =?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 [this message]
2001-08-23 15:59 ` Tom Rini
2001-08-23 19:26 ` Jes Sorensen
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
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=01082309554604.03507@widmers.oce.srci.oce.int \
--to=menion@srci.iwpsd.org \
--cc=glamm@mail.ece.umn.edu \
--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
Powered by JetHome