From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: #!/usr/bin/env in containers, or something
Date: Wed, 26 Oct 2016 14:09:41 +0200
Message-ID: <87oa27tipm.fsf@gnu.org>
References: <878tth1pio.fsf@dustycloud.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47541)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bzN1h-0003Uq-1v
	for guix-devel@gnu.org; Wed, 26 Oct 2016 08:09:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bzN1c-0006Ho-4S
	for guix-devel@gnu.org; Wed, 26 Oct 2016 08:09:49 -0400
In-Reply-To: <878tth1pio.fsf@dustycloud.org> (Christopher Allan Webber's
	message of "Fri, 21 Oct 2016 14:16:31 -0500")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org

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 =E2=80=98guix environment --container=E2=80=
=99 could have
an option to create /usr/bin/env:

  https://lists.gnu.org/archive/html/guix-devel/2015-11/msg00527.html

=E2=80=98--expose=E2=80=99 already allows this, so essentially we=E2=80=99d=
 provide a shorter
option and take =E2=80=98env=E2=80=99 from the current =E2=80=98coreutils=
=E2=80=99 package=E2=80=94similar to
how /bin/sh links to the current =E2=80=98bash=E2=80=99 already.

How does that sound?

Ludo=E2=80=99.