all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Rob Vermaas <rob.vermaas@gmail.com>
Cc: nix-dev <nix-dev@cs.uu.nl>, bug-guix@gnu.org
Subject: Re: Down with /bin/sh!
Date: Thu, 03 Jan 2013 17:27:28 +0100	[thread overview]
Message-ID: <87k3ru1bbj.fsf@gnu.org> (raw)
In-Reply-To: <CAJuVCXt+pOLKDJrCQDv0tMaNSRFjDuu5SBWRsdCM4OcbJAdi8A@mail.gmail.com> (Rob Vermaas's message of "Thu, 3 Jan 2013 17:00:50 +0100")

Hi Rob!

Rob Vermaas <rob.vermaas@gmail.com> skribis:

>   • Right after unpacking a source tarball, all the source files go
>>     through ‘patch-shebang’, which replaces any #!/bin/sh and similar
>>     with the right path.
>>
>
> I would not like such a change in stdenv of nixpkgs, without an option to
> disable this. For example, we use nix to build some packages that run
> outside of nix, and for those, we do not want to replace all the references
> to /bin/sh in all source files/scripts.

I’m not sure what you mean by “run outside of Nix”.

The files that are patched are source files anyway.  Nixpkgs already has
a patch-shebang phase for installed files, which is what users notice.

> I haven't thought of it much, but in general I would like an approach
> better that would *not* change the source code of packages by default,
> but only when it is really necessary.

Well yeah, it’s a bit of a sledgehammer approach.  Still, it works
like a charm, and feels just like a natural extension of all our
craziness.  :-)

Thanks,
Ludo’.
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

      reply	other threads:[~2013-01-03 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 15:14 Down with /bin/sh! Ludovic Courtès
2013-01-03 16:00 ` Rob Vermaas
2013-01-03 16:27   ` Ludovic Courtès [this message]

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=87k3ru1bbj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nix-dev@cs.uu.nl \
    --cc=rob.vermaas@gmail.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 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.