Re: [PATCH 0/2] Make run-command.c honour SHELL_PATH
- From
Ben Walton <bwalton@artsci.utoronto.ca>
- Date
- Mar 26, 2012, 18:19 UTC
- Message-ID
- <1332785666-sup-5513@pinkfloyd.chass.utoronto.ca>
- In-Reply-To
- <20120326181238.GH7942@sigill.intra.peff.net>
Excerpts from Jeff King's message of Mon Mar 26 14:12:38 -0400 2012:
> What is /opt/csw/bin/sh? Is it a symlink to bash (which would mean > bash running in POSIX mode)? Or is it a lightweight shell like ash? > Or something else?
This is some version of the traditional solaris /bin/sh packaged as part of schilyutils (Joerg Schilling's utilities). I'm really not sure why he packages it or what the differences from /bin/sh are...Asking him is on my todo list though. I only just learned it existed when I hit this glitch.
Show 6 quoted lines
> The point of SHELL_PATH is to provide a POSIX shell. Generally, > bash behavior is a superset of POSIX, so you will not run into any > incompatibilities by running things with bash. But do be aware that > you are slightly incompatible with the rest of the world (so things > that work for you, for example, might not work for people using git > with the stock "shell is /bin/sh" configuration).
This was a conscious choice I made early in the packaging of git for OpenCSW. The idea was that we had a shell that was also under our packaging control and 'sane' at the same time. I realize it's a superset of the POSIX functionality. It's something I should maybe change, but I'd need to stage it slowly so as to avoid breakages.
Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302