git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
To: Sean <seanlkml@sympatico.ca>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: /bin/sh portability question
Date: Sun, 25 Sep 2005 21:26:08 +0200	[thread overview]
Message-ID: <20050925192608.GD19023@schottelius.org> (raw)
In-Reply-To: <39450.10.10.10.28.1127471685.squirrel@linux1>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

Sean [Fri, Sep 23, 2005 at 06:34:45AM -0400]:
> On Fri, September 23, 2005 5:19 am, Junio C Hamano said:
> > "Sean" <seanlkml@sympatico.ca> writes:
> >
> >> If not, would you accept a patch that first converted the shell scripts
> >> to
> >> #!/bin/bash and then added a "make install" option that allowed them to
> >> be
> >> replaced?   Something like "make install S=/bin/ash" for instance?
> >
> >     $ make SHELL_PATH=/bin/bash
> >
> > Perhaps?
> >
> 
> Heh.. so you've already got that working :o)   So on Solaris one fix would
> be to just use the SHELL_PATH setting when installing to point to
> /bin/bash.   What do you think about making /bin/bash the default?

I think it's a bad idea, because some systems do not have and want bash,
because it's unneeded. On all systems here we've ash as /bin/sh and
/bin/zsh as primary user shell. Thus, /bin/bash does not exist, because
it's not as comfortable as zsh and not as small as ash.

Nico,
   who really likes man bash (very well documentated), but not the shell itself

-- 
Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
Open Source nutures open minds and free, creative developers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2005-09-25 19:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  7:50 /bin/sh portability question Peter Eriksen
2005-09-23  8:24 ` Junio C Hamano
     [not found]   ` <54643.10.10.10.28.1127466177.squirrel@linux1>
2005-09-23  9:02     ` Sean
2005-09-23  9:19       ` Junio C Hamano
     [not found]         ` <39450.10.10.10.28.1127471685.squirrel@linux1>
2005-09-23 10:34           ` Sean
2005-09-25 19:26           ` Nico -telmich- Schottelius [this message]
     [not found]             ` <33541.10.10.10.28.1127677005.squirrel@linux1>
2005-09-25 19:36               ` Sean
2005-09-23  9:07 ` Junio C Hamano
2005-09-23 12:17   ` Peter Eriksen
2005-09-24  1:13     ` Junio C Hamano
     [not found]       ` <20050924195029.GA20514@bohr.gbar.dtu.dk>
2005-09-24 21:31         ` Junio C Hamano
2005-09-24 17:35   ` Patrick Mauritz
2005-09-23 19:48 ` H. Peter Anvin
2005-09-23 19:55   ` Morten Welinder
2005-09-23 19:57   ` Joel Becker
2005-09-23 20:00     ` H. Peter Anvin

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=20050925192608.GD19023@schottelius.org \
    --to=nico-linux-git@schottelius.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=seanlkml@sympatico.ca \
    /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;
as well as URLs for NNTP newsgroup(s).