From: Kyle <kyle@posteo.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Alternatives to --emulate-fhs on foreign distros
Date: Fri, 21 Apr 2023 15:44:09 +0000 [thread overview]
Message-ID: <D7430D83-3252-4E58-99D6-D82DB85091D3@posteo.net> (raw)
In-Reply-To: <87ttxayank.fsf@gmail.com>
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, maybe that's not that helpful if /bin/bash was made available?
On April 20, 2023 8:56:47 AM EDT, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>Hi Kyle,
>
>Kyle Andrews <kyle@posteo.net> 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 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?
>
>Use /usr/bin/env. It's available on all mainstream distributions, and
>it's also available on Guix System, so it should work everywhere.
>
>--
>Thanks,
>Maxim
next prev parent reply other threads:[~2023-04-21 16:10 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D7430D83-3252-4E58-99D6-D82DB85091D3@posteo.net \
--to=kyle@posteo.net \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.