From: David Weinehall <tao@acc.umu.se>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Patch for Menuconfig script
Date: Thu, 11 Jul 2002 01:13:35 +0200 [thread overview]
Message-ID: <20020710231335.GG29001@khan.acc.umu.se> (raw)
In-Reply-To: <21071.1026168807@ocs3.intra.ocs.com.au>
On Tue, Jul 09, 2002 at 08:53:27AM +1000, Keith Owens wrote:
> On Mon, 8 Jul 2002 08:14:12 -0700,
> Tom Rini <trini@kernel.crashing.org> wrote:
> >On Sun, Jul 07, 2002 at 11:22:10PM +0100, Riley Williams wrote:
> >> > This is just a patch to the Menuconfig script (can be easily adapted
> >> > to the other ones) that allows you to configure the kernel without
> >> > the requirement of bash (I tested it with ksh, in POSIX-only mode).
> >> > Feel free to flame me :P
> >>
> >> Does it also work in the case where the current shell is csh or tcsh
> >> (for example)?
> >
> >Er.. why wouldn't it?
> >$ head -1 scripts/Menuconfig
> >#! /bin/sh
>
> The #! line is irrelevant. The script is invoked via
>
> $(CONFIG_SHELL) scripts/Menuconfig arch/$(ARCH)/config.in
>
> Large chunks of kbuild assume that CONFIG_SHELL is bash. Don't bother
> trying to cleanup all the code that assumes bash, just
> make CONFIG_SHELL=/path/to/bash ...
As long as the new, bash-ignorant code is as good as the old one, and
works equally well with bash and hopefully better with other shells,
I see no harm, and a lot of benefit, in accepting the patch.
Yes, a lot of code assumes bash is there, but unlike the case of gcc,
there are good alternatives. Let us enable people who use
ksh/tcsh/rc/whatever as their main shell to remove the bash they keep
installed simply to be able to build their kernels.
For those who wonders: I use bash, nothing else. Still I think it is
silly to argue against this kind of patches because a lot of other
parts of the build-system/config-systems till depends on bash.
Getting rid of the bash:isms everywhere is far from impossible; look at
Debian, they are mostly there.
/David
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2002-07-10 23:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 1:05 Justin Hibbits
2002-07-07 22:22 ` Riley Williams
2002-07-08 15:14 ` Tom Rini
2002-07-08 15:22 ` Justin R Hibbits
2002-07-08 17:44 ` Riley Williams
2002-07-08 18:18 ` Tom Rini
2002-07-11 20:06 ` Riley Williams
2002-07-11 20:23 ` Tom Rini
2002-07-08 22:53 ` Keith Owens
2002-07-08 23:27 ` Sanctus Evanidus
2002-07-08 23:40 ` Thunder from the hill
2002-07-10 23:13 ` David Weinehall [this message]
2002-07-10 23:40 ` HDD test bench Mukesh Rajan
2002-07-10 23:49 ` Mr. James W. Laferriere
2002-07-11 7:35 ` Patch for Menuconfig script Adrian Bunk
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=20020710231335.GG29001@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=kaos@ocs.com.au \
--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®