On Friday, April 21, 2023 2:35:30 PM EDT Kyle wrote:
> Its kind of hard to test. The easiest I have managed has been to see that I
> don't get the error with --emulate-fhs in my call, and the script that
> fails starts with:
>
> #!/usr/bin/env txr
>
> To simplify things, I made a self contained t
Thanks so much! That is perfect.
On April 22, 2023 4:36:08 PM EDT, Maxim Cournoyer
wrote:
>Hi Kyle,
>
>Kyle writes:
>
>> Dear Maxim,
>>
>> Unfortunately, I don't see /usr/bin/env when I look inside the file system
>> resulting from:
>>
>> guix shell coreutils --container
>>
>
>For this use ca
Hi Kyle,
Kyle writes:
> Dear Maxim,
>
> Unfortunately, I don't see /usr/bin/env when I look inside the file system
> resulting from:
>
> guix shell coreutils --container
>
For this use case, I use the --symlink option, like so:
'--symlink=/usr/bin/env=bin/env'.
--
Thanks,
Maxim
Note that the easiest standalone TXR script I could think of is:
```
#!/usr/bin/env txr
#(output)
Hi
@(end)
```
I am betting you probably could include that in a package to reproduce the
issue.
On April 21, 2023 2:35:30 PM EDT, Kyle wrote:
>Its kind of hard to test. The easiest I have managed
Its kind of hard to test. The easiest I have managed has been to see that I
don't get the error with --emulate-fhs in my call, and the script that fails
starts with:
#!/usr/bin/env txr
To simplify things, I made a self contained txr script and wrapped that up in
my test R package. Sure enough,
Dear Maxim,
Unfortunately, I don't see /usr/bin/env when I look inside the file system
resulting from:
guix shell coreutils --container
I don't understand how to apply "system" configuration to a guix shell
container other than crudely through --emulate-fhs. Since noone has needed it
so far,
Kyle Andrews writes:
> You are right about this. I created a minimal reproducible R package with a
> basic shell script included and the shebangs were patched. I'm still trying
> to figure out the actual cause of my shell errors.
Perhaps try using ``shellcheck''.
"(" writes:
> Kyle writes:
>> 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 patch
Hey :)
While slightly of topic, I have to wonder about:
On 2023-04-19 06:18:33 +, Kyle Andrews wrote:
> The main bashism I use is default environment variables ${FOO:-bar}.
I'm pretty sure that is just regular POSIX compatible syntax no? At least if I
read [0] correctly.
0:
https://pubs.op
Hi Kyle,
Kyle Andrews writes:
> Dear Guix,
>
> 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 w
Kyle writes:
> 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 m
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
"(" writes:
> ``/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.)
...never mind, i thought you were talking about software that you want
to package.
Kyle Andrews 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. M
Hi,
So everything is bash in the end, but I do not know whether bash behaves
differently if it is called under the name "sh". You could give it a try.
Yes. Search for \bsh\b in the manpage. It includes things like
If bash is invoked with the name sh, it tries to mimic the startup be‐
havio
Hello,
Am Wed, Apr 19, 2023 at 06:18:33AM + schrieb Kyle Andrews:
> I'm curious what other options might be. The main bashism I use is default
> environment variables ${FOO:-bar}. On a native Guix system I could just add
> /usr/bin/env back in. However, that doesn't seem to be possible with
Dear Guix,
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 s
17 matches
Mail list logo
