From: Ricardo Wurmus <rekado@elephly.net>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: thesis: guixsd should provide /usr/bin/env
Date: Tue, 17 Nov 2015 07:48:56 +0100 [thread overview]
Message-ID: <8737w5nmsn.fsf@elephly.net> (raw)
In-Reply-To: <874mgmti7b.fsf@igalia.com>
Andy Wingo <wingo@igalia.com> writes:
> I think GuixSD should follow NixOS's lead and provide /usr/bin/env. The
> reason is to support scripts that can run either on GuixSD or on some
> other system. For example instead of:
>
> #!/bin/bash
>
> we can do
>
> #!/usr/bin/env bash
>
> So we just need /usr/bin/env in the root and nothing else.
>
> Alternately, I am not sure if this would work but we could make a form
> of "guix environment" which populates a profile that is mounted at /usr
> in a container. That would allow many more non-Guix tools to run.
>
> WDYT?
I just did this on GuixSD:
sudo -E guix package -p /usr -i bash coreutils
Now I have /usr/bin/env and /usr/bin/bash. I don’t think I needed it
before, though. “guix environment” is probably not the appropriate tool
for this.
I think it’s better to do this explicitly with profiles than to treat
/usr/bin/env somehow specially. Providing /usr/bin/env doesn’t
necessarily help — one would still have to have an interpreter installed
in an active profile.
~~ Ricardo
next prev parent reply other threads:[~2015-11-17 6:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 9:19 thesis: guixsd should provide /usr/bin/env Andy Wingo
2015-11-17 6:48 ` Ricardo Wurmus [this message]
2015-11-19 16:07 ` Ludovic Courtès
2015-11-19 17:35 ` Andy Wingo
2015-11-20 14:00 ` Ludovic Courtès
2015-11-20 15:58 ` Andy Wingo
2016-02-17 7:31 ` 宋文武
2016-02-17 7:52 ` Jookia
2016-02-29 9:41 ` Ludovic Courtès
2016-02-29 9:46 ` Ludovic Courtès
2016-02-29 18:11 ` Christopher Allan Webber
2016-03-01 8:09 ` Andy Wingo
2016-03-01 8:11 ` Jookia
2016-03-03 17:00 ` Ludovic Courtès
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=8737w5nmsn.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).