From: Kyle Andrews <kyle@posteo.net>
To: "(" <paren@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Alternatives to --emulate-fhs on foreign distros
Date: Thu, 20 Apr 2023 22:32:36 +0000 [thread overview]
Message-ID: <87h6ta18m8.fsf@posteo.net> (raw)
In-Reply-To: <87sfcvybal.fsf@disroot.org>
"(" <paren@disroot.org> writes:
> Kyle <kyle@posteo.net> 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 me how thorough Guix is being at finding these.
>
> Hmm. Can you show me an example of one of these scripts? (The
> R-BUILD-SYSTEM *does* seem to include 'PATCH-SHEBANGS...)
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.
next prev parent reply other threads:[~2023-04-20 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 6:18 Alternatives to --emulate-fhs on foreign distros Kyle Andrews
2023-04-19 8:08 ` Andreas Enge
2023-04-19 13:05 ` Martin Castillo
2023-04-19 15:10 ` (
2023-04-19 15:18 ` (
2023-04-19 17:24 ` Kyle
2023-04-19 18:30 ` (
2023-04-20 22:32 ` Kyle Andrews [this message]
2023-04-21 5:36 ` (
2023-04-21 18:35 ` Kyle
2023-04-21 18:57 ` Kyle
2023-05-21 4:32 ` Philip McGrath
2023-04-20 12:56 ` Maxim Cournoyer
2023-04-21 15:44 ` Kyle
2023-04-22 20:36 ` Maxim Cournoyer
2023-04-27 2:16 ` Kyle
2023-04-20 19:51 ` wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ta18m8.fsf@posteo.net \
--to=kyle@posteo.net \
--cc=help-guix@gnu.org \
--cc=paren@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).