unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Enge <andreas@enge.fr>
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 10:08:53 +0200	[thread overview]
Message-ID: <ZD+hlYCHNwq07QSX@jurong> (raw)
In-Reply-To: <87cz407482.fsf@posteo.net>

Hello,

Am Wed, Apr 19, 2023 at 06:18:33AM +0000 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 only Guix shell. Maybe I am wrong here?

as an exception to the rule, a Guix system contains /bin/sh, which on my
machine looks like this:

$ ll /bin
lrwxrwxrwx 1 root root  2  5. Nov 2019  bash -> sh
lrwxrwxrwx 1 root root 61 17. Apr 09:51 sh -> /gnu/store/d99ykvj3axzzidygsmdmzxah4lvxd6hw-bash-5.1.8/bin/sh

$ ll /gnu/store/d99ykvj3axzzidygsmdmzxah4lvxd6hw-bash-5.1.8/bin
-r-xr-xr-x 2 root root 951344  1. Jan 1970  bash
-r-xr-xr-x 1 root root   6791  1. Jan 1970  bashbug
lrwxrwxrwx 1 root root      4  1. Jan 1970  sh -> bash

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.

Andreas



  reply	other threads:[~2023-04-19  8:09 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 [this message]
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
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=ZD+hlYCHNwq07QSX@jurong \
    --to=andreas@enge.fr \
    --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).