public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier <0@pervalidus.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Will 2.6 require Python for any configuration ? (CML2)
Date: Wed, 22 Aug 2001 03:08:07 -0300	[thread overview]
Message-ID: <20010822030807.N120@pervalidus> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1017 bytes --]

Am I the only one afraid that the Python requirement can turn
into a problem ? You can develop anything on Linux without
Python. I'd compare Python to Tcl - you only install it to
waste space, develop, or run applications that use it. Perl
is very different. It's required by GNU Automake and more.

I'm really surprised by the fact that nobody noticed what a
nightmare 2.6 will be with such a requirement. You can't
expect everybody to install something that's of no use for
most.

My intention isn't to diminish the importance of CML2 and the
hard and volunteer work of Eric S. Raymond. I just can't
consider Python a requirement to configure the build process
of a Kernel.

Please, consider using the actual setup if Python isn't
installed.

PS: I install Python at home to use a single application.
BTW, I compiled Python and... the curses module isn't enabled
by default. You have to edit Setup. Another possible problem
for menuconfig.

-- 
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-2717-2399 (Niterói-RJ BR)

             reply	other threads:[~2001-08-22  6:07 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22  6:08 =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier [this message]
2001-08-23 12:05 ` Will 2.6 require Python for any configuration ? (CML2) 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
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=20010822030807.N120@pervalidus \
    --to=0@pervalidus.net \
    --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