unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Olivier Dion via <help-guix@gnu.org>
Cc: jordi <jordila@librebits.info>,  Olivier Dion <olivier.dion@polymtl.ca>
Subject: Re: bash scripts in Guix question
Date: Tue, 04 Oct 2022 23:38:57 -0400	[thread overview]
Message-ID: <871qrnj5wu.fsf@gmail.com> (raw)
In-Reply-To: <871qrnk61s.fsf@laura> (Olivier Dion via's message of "Tue, 04 Oct 2022 10:38:23 -0400")

Hi,

Olivier Dion via <help-guix@gnu.org> writes:

> On Tue, 04 Oct 2022, jordi <jordila@librebits.info> wrote:
>> Hi guixers,
>>
>> i'm wondering...for my scripts to work in Guix, instead of
>>  '#!	/bin/bash' , 
>>
>
> Typically the `sh' program should be a symlinked to `bash' in your
> system profile.  I think it is the case for many distro.  If you want it
> to be bulletproof though for other distros maybe something like that:
>
> #!/bin/sh
> if [ "$(basename $SHELL)" != "bash" ]; then
>   exec bash "$0" "$@"
> fi
>
> echo "hey!"

I prefer the "#!/usr/bin/env bash" shebang; /usr/bin/env is available on
FHS distribution, and on Guix System, for convenience.  You can use if
for any interpreted script, such as Guile, Python, Perl, etc.

-- 
Thanks,
Maxim


  reply	other threads:[~2022-10-05  3:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 13:18 bash scripts in Guix question jordi
2022-10-04 14:10 ` Ekaitz Zarraga
2022-10-04 14:31 ` Fulbert
2022-10-04 14:38 ` Olivier Dion via
2022-10-05  3:38   ` Maxim Cournoyer [this message]
2022-10-05  3:58     ` Olivier Dion via
2022-10-05  9:48       ` bash scripts in Guix question - suspend ? jordi
2022-10-05 10:29         ` Tobias Geerinckx-Rice
2022-10-06  0:43       ` bash scripts in Guix question Maxim Cournoyer
2022-10-06  0:56         ` Olivier Dion via

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=871qrnj5wu.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jordila@librebits.info \
    --cc=olivier.dion@polymtl.ca \
    /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).