From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: #!/usr/bin/env in containers, or something
Date: Wed, 26 Oct 2016 14:09:41 +0200 [thread overview]
Message-ID: <87oa27tipm.fsf@gnu.org> (raw)
In-Reply-To: <878tth1pio.fsf@dustycloud.org> (Christopher Allan Webber's message of "Fri, 21 Oct 2016 14:16:31 -0500")
Christopher Allan Webber <cwebber@dustycloud.org> skribis:
> I'm currently looking at building a version of coreboot. Unfortunately,
> the mortal enemy of every GuixSD user, #!/usr/bin/env, lurks around
> every corner.
>
> Wingo made an interesting suggestion on IRC today: maybe we could have
> some "guix environment --container" CLI mapping /usr/bin/env.
>
> I know we want "purity" and it's annoying that /usr/bin/env even exists,
> but there are times where you're trying to do some development on some
> upstream package, and it's not possible if you can't get /usr/bin/env
> into your development environment. Sinc we can make containers --pure,
> I think it would be okay to have /usr/bin/env in this circumstance.
>
> What do people think?
There was some consensus that ‘guix environment --container’ could have
an option to create /usr/bin/env:
https://lists.gnu.org/archive/html/guix-devel/2015-11/msg00527.html
‘--expose’ already allows this, so essentially we’d provide a shorter
option and take ‘env’ from the current ‘coreutils’ package—similar to
how /bin/sh links to the current ‘bash’ already.
How does that sound?
Ludo’.
next prev parent reply other threads:[~2016-10-26 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 19:16 #!/usr/bin/env in containers, or something Christopher Allan Webber
2016-10-26 12:09 ` Ludovic Courtès [this message]
2016-10-26 16:30 ` Christopher Allan Webber
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=87oa27tipm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
/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).