all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: services: Add ‘/usr/bin/env’ special file.
Date: Sat, 07 Sep 2019 09:52:35 +0200	[thread overview]
Message-ID: <87lfv0wnjw.fsf@nckx> (raw)
In-Reply-To: <6384138c4454d584c43e0a6144ed18bf458c551a.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

Jesse,

Thanks!  It was linked from another thread[0] Ludo' pasted to my 
patch, though.  I've read both.

Jesse Gibbons 写道:
> Here's a post with what I think is a good argument against 
> adding
> /usr/bin/env. I think the standard patch-shebang phase does a 
> good job
> at preventing the potential issue, but the argument still 
> applies to

So is the argument here that Guix packages would generate scripts 
at run-time that refer to /usr/bin/env?  Or just that it's 
currently easy to catch packages that install #!/usr/bin/env 
scripts?  Or something else?

Neither /bin/sh nor /usr/bin/env are available in the build 
environment.  Relying on the *likely* run-time non-existence of 
/usr/bin/env in *user* environments to catch *packaging* bugs does 
not sound acceptable to me.

> scripts generated by make, as I learned while attempting to port
> pysolfc.

If you have the time, could you elaborate?

Kind regards,

T G-R

[0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35910

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2019-09-07  7:53 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. [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfv0wnjw.fsf@nckx \
    --to=guix-devel@gnu.org \
    --cc=jgibbons2357@gmail.com \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.