From: "Ludovic Courtès" <ludo@gnu.org>
To: Bengt Richter <bokr@bokr.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: services: Add ‘/usr/bin/env’ special file.
Date: Mon, 09 Sep 2019 10:13:00 +0200 [thread overview]
Message-ID: <87woeh28hf.fsf@gnu.org> (raw)
In-Reply-To: <20190909070144.GA5717@PhantoNv4ArchGx.localdomain> (Bengt Richter's message of "Mon, 9 Sep 2019 00:01:44 -0700")
Hi Bengt,
Bengt Richter <bokr@bokr.com> skribis:
> On +2019-09-09 00:07:10 +0200, Ludovic Courtès wrote:
[...]
>> Like I wrote in <https://issues.guix.gnu.org/issue/35910#2> and in the
>> message it refers to, although I was initially mildly reluctant to
>> having /usr/bin/env by default, I’ve come to think that lack of
>> /usr/bin/env is a gratuitous annoyance—not to me of course, but to
>> newcomers as we’ve seen repeatedly, be they seasoned GNU/Linux users or
>> not.
>>
>> With that in mind, adding /usr/bin/env by default is probably a good move.
>>
>
> Hi Ludo,
>
> I may be one of those (over-) seasoned (past best-before) users you mention :)
> -- but with all due respect, is this not a compromise of the fundamental
> idea of guix _transactional_ package management?
No it’s not. It really doesn’t change anything.
First, you can always opt out—the discussion was about whether it should
remain opt-in, or whether it should become opt-out.
Second, and more importantly: packages (“derivations”) are still built
in an isolated environment that does not and will never contain
/usr/bin/env.
Sorry I’m not replying to your other points now, but I hope it clarifies
things!
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-09-09 8:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190906102509.28951.2772@vcs0.savannah.gnu.org>
[not found] ` <20190906102510.002BE21324@vcs0.savannah.gnu.org>
2019-09-06 10:36 ` 01/01: services: Add ‘/usr/bin/env’ special file Christopher Baines
2019-09-06 10:44 ` pelzflorian (Florian Pelz)
2019-09-06 10:47 ` pelzflorian (Florian Pelz)
2019-09-06 15:54 ` Tobias Geerinckx-Rice
2019-09-06 23:21 ` Mark H Weaver
2019-09-07 5:05 ` Jesse Gibbons
2019-09-07 7:52 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution.
2019-09-07 15:33 ` Jesse Gibbons
2019-09-07 10:06 ` Tobias Geerinckx-Rice
2019-09-07 15:03 ` Jesse Gibbons
2019-09-08 21:48 ` Ludovic Courtès
2019-09-08 23:53 ` Jesse Gibbons
2019-09-08 22:19 ` Tobias Geerinckx-Rice
2019-09-06 23:47 ` Mark H Weaver
2019-09-07 8:54 ` Tobias Geerinckx-Rice
2019-09-07 14:41 ` Marius Bakke
2019-09-07 17:56 ` Ricardo Wurmus
2019-09-08 11:55 ` Konrad Hinsen
2019-09-08 18:31 ` Hartmut Goebel
2019-09-08 22:07 ` Ludovic Courtès
2019-09-09 7:01 ` Bengt Richter
2019-09-09 8:13 ` Ludovic Courtès [this message]
2019-09-09 1:37 ` Chris Marusich
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=87woeh28hf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bokr@bokr.com \
--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).