[Slackbuilds-users] brace expansion

Eugen Wissner belka at caraus.de
Wed Jun 16 19:09:19 UTC 2021

I changed /bin/sh to /bin/dash on all my machines months ago and it
works perfectly. My patch to slackpkg to replace /bin/sh with
/bin/bash was accepted. Pat changed /bin/sh to /bin/bash in all
rc-scripts, so they work with other shells.

So there is an ongoing effort to make everything work with other shells.
Currently I get random build errors and have to restart the script
with "bash xyz.SlackBuild" to see if it fixes the problem.

On Wed, Jun 16, 2021 at 02:55:55PM -0400, B Watson wrote:
> On 6/16/21, Eugen Wissner <belka at caraus.de> wrote:
> > Many Slackbuilds use brace expansion (mkdir {a,b}), which is a bashism.
> > Can we fix this? I would help with patches if the change is desirable.
> What makes you say it's broken and needs fixing?
> SlackBuild scripts have #!/bin/sh at the top, yes. But they only have
> to work on Slackware. And, /bin/sh on Slackware *has to be* a symlink
> to /bin/bash. If you don't believe me, try changing it to ash, ksh,
> or zsh, then rebooting the box.
> Personally I'd prefer if SlackBuild scripts started with #!/bin/bash,
> but when I used to submit them that way, the admins would change it
> back to #!/bin/sh. So I quit worrying about it, and the world didn't
> end.
> Now, if the use of bashisms actually caused real problems (build
> failures), that would be worth looking into. But changing a bunch of
> scripts just to comply with what amounts to OCD... IMO not worth even
> thinking about.
> I'm just one opinionated guy though. What does the rest of the list
> think?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

More information about the SlackBuilds-users mailing list