[Slackbuilds-users] Patch proposal to remove bashisms from some scripts

King Beowulf kingbeowulf at gmail.com
Mon Nov 1 13:07:28 UTC 2010

I would say so.

My 2 cents: SBo hosts packages for Slackware. Slackware default shell
is bash. Slackbuild scripts should be bash compliant.  Anything else
is an exercise for the end user (eg dependency resolution etc).

Personally, I have a hard enough time keeping up with bash; I have no
interest in the globs of other shells out there.


On 11/1/10, R. Andrew Bailey <bailey at akamai.com> wrote:
> On 01/11/10 08:00 -0400, David Spencer wrote:
>>>  Don't you think its a lot easier for you to remember to exec these
>>>  scripts with bash, than to get everybody else to change their scripts
>>>  to work with your symlink? :)
>>Technical measures are always better than "remembering". That's what
>>"#!/bin/bash" is for.
>>What follows is just a personal opinion. I try to write my scripts to
>>the highest standards. If I start with #!/bin/sh, and then I write a
>>bashism, then #!/bin/sh was a lie, and when someone points that out, I
>>am embarassed and grateful, especially when the fix is really, really
>>easy.  I'm not "everybody", but then, not everybody's script starts
>>with a lie.  Just three of mine :-/
> So changing the shbang lines to read #!/bin/bash would suffice, no?
>   .andy
>>SlackBuilds-users mailing list
>>SlackBuilds-users at slackbuilds.org
>>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>FAQ - http://slackbuilds.org/faq/
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/

Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

More information about the SlackBuilds-users mailing list