The context is that my R package calls a bunch of shell scripts stored inside
it. I am getting errors about /usr/bin/env not being available (e.g. bad
interpreter: no such file or directory), so was thinking that their shebangs
were not getting patched. It's not clear to me how thorough Guix is being at
finding these.
On April 19, 2023 11:10:44 AM EDT, "(" <pa...@disroot.org> wrote:
>
>Kyle Andrews <k...@posteo.net> writes:
>> The (many) shell scripts in my software depend on bashisms. In the code right
>> now I typically use /usr/bin/env bash since I had read that was the most
>> portable way of referencing a shell. However, I really don't think I have a
>> good
>> handle on what my choices are. Maybe the tedious solution of just typing
>> `bash
>> script.sh' in all of the system calls referencing this scripts might be the
>> right approach in the long run?
>
>``/usr/bin/env bash'' will automatically be substituted for the path to
>an available ``/bin/bash'' in the store. (If that's what you're talking
>about here; not sure what the context is exactly.)
