From: "(" <paren@disroot.org>
To: Kyle Andrews <kyle@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: Alternatives to --emulate-fhs on foreign distros
Date: Wed, 19 Apr 2023 16:10:44 +0100 [thread overview]
Message-ID: <875y9rzz1n.fsf@disroot.org> (raw)
In-Reply-To: <87cz407482.fsf@posteo.net>
Kyle Andrews <kyle@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.)
next prev parent reply other threads:[~2023-04-19 15:13 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 ` ( [this message]
2023-04-19 15:18 ` (
2023-04-19 17:24 ` Kyle
2023-04-19 18:30 ` (
2023-04-20 22:32 ` Kyle Andrews
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=875y9rzz1n.fsf@disroot.org \
--to=paren@disroot.org \
--cc=help-guix@gnu.org \
--cc=kyle@posteo.net \
/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).