mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Glamm <glamm@mail.ece.umn.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: Will 2.6 require Python for any configuration ? (CML2)
Date: Thu, 23 Aug 2001 10:36:20 -0500	[thread overview]
Message-ID: <20010823103620.A6965@kittpeak.ece.umn.edu> (raw)
In-Reply-To: <20010822030807.N120@pervalidus> <20010823140555.A1077@newton.bauerschmidt.eu.org>
In-Reply-To: <20010823140555.A1077@newton.bauerschmidt.eu.org>; from rb@debian.org on Thu, Aug 23, 2001 at 02:05:55PM +0200

> > 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.
> 
> Well, I don't know the details of the plans, but IMHO is a dependency to
> python for configuring the kernel not unreasonable. Nowadays a lot of
> people don't even compile their kernels themselves, and thus not
> _everybody_ is required to have python installed. When using make

I bet the same number of people still compile their own kernels.
However, the *percentage* of people that still compile their own
kernels probably keeps shrinking as the number of people using
Linux increases.

The same argument applies now that applies when this argument first
started when ESR announced CML to the list: my '386 with 8MB of
RAM and it's 20MB of disk doesn't have the room (or speed, for
that matter) to install the fad interpreted language of today.
Besides, it'll take me 45 minutes to download the latest version
of Python over my 28.8k modem.  And yes, I download the kernel patch
by patch to minimize the download pain ;)

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.

> menuconfig you are also required to have curses development files
> installed even if you don't need them for anything else. Python also is
> of (fast) growing popularity, and for example in Debian (I don't know
> about other distributions, but I suppose it's similar there) Python is
> Priority: standard (whereas libncurses5-dev surely isn't). 

Believe it or not, there are people like me that take a distribution,
do a minimal install just to get a machine up and running, then remove
most of the package management software from the installation once
networking has been configured, then continually update software
from source as new fixes are released.  I managed to update an
early version of Slackware from the earliest libc4 releases through
libc6 without ever touching a distribution disk - all updated through
source.

But I would expect that I'm in the minority in this regard. ;)

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.

-Bob

  reply	other threads:[~2001-08-23 15:36 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 [this message]
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
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=20010823103620.A6965@kittpeak.ece.umn.edu \
    --to=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

all inboxes | Powered by JetHome®