From: Olivier Dion via <help-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Olivier Dion via <help-guix@gnu.org>, jordi <jordila@librebits.info>
Subject: Re: bash scripts in Guix question
Date: Wed, 05 Oct 2022 20:56:14 -0400 [thread overview]
Message-ID: <87pmf593dd.fsf@laura> (raw)
In-Reply-To: <87tu4hixwx.fsf@gmail.com>
On Wed, 05 Oct 2022, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Hi,
>
> Olivier Dion <olivier.dion@polymtl.ca> writes:
>
> [...]
>
>>> 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.
>>
>> Only if coreutils is in the profile that would work yes.
>
> coreutils doesn't need to be in the profile since /usr/bin/env is linked
> to (file-append coreutils "bin/env"); see in the value of %base-services
> in (gnu services base), which contains:
>
> --8<---------------cut here---------------start------------->8---
> (service special-files-service-type
> `(("/bin/sh" ,(file-append bash "/bin/sh"))
> ("/usr/bin/env" ,(file-append coreutils "/bin/env"))))
> --8<---------------cut here---------------end--------------->8---
Oh interesting I did not know that. Thank you!
--
Olivier Dion
oldiob.dev
prev parent reply other threads:[~2022-10-06 0:57 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
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 [this message]
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=87pmf593dd.fsf@laura \
--to=help-guix@gnu.org \
--cc=jordila@librebits.info \
--cc=maxim.cournoyer@gmail.com \
--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).