Yeah, I also use dash as my /bin/sh and I sometimes encounter this and it's a little annoying to be honest. I mean, if you already use /bin/sh as the shebang line, technically you are expected to write POSIX-compliant shell scripts, even though it will still work correctly when having /bin/sh linked to bash. Not trying to bash on the maintainers here (thanks for all the hard work!), It's just a little bit unfortunate.
I personally prefer that the scripts are updated to not use the brace expansion so I can use a more lightweight shell to run the script :D. But, I understand that some scripts are too complex to be converted to POSIX-compliant ones so it's just easier to use /bin/bash as the shebang line, like what Mr. Volkerding did with some of Slackware's core utilities. I'm happy with either decision, as long as I can rest assured that no scripts will fail randomly because of using the wrong shell :D. MMS On Thu, Jun 17, 2021, 02:51 Spycrowsoft <[email protected]> wrote: > > Op 16-06-2021 om 21:09 schreef Eugen Wissner: > > Pat changed /bin/sh to /bin/bash in all > > rc-scripts, so they work with other shells. > > We should confirm this with Patrick Volderding, but if he's doing that, > my take on the matters is: "Follow what the BDFL is doing". > > The fact that the SlackBuild contains a pointer to the right shell also > makes sense to me. > _______________________________________________ > SlackBuilds-users mailing list > [email protected] > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > >
_______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
