nixpkgs/pkgs/development
Jörg Thalheim c8ff4a92f7 treewide: use runtimeShell instead of stdenv.shell whenever possible
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.

(cherry picked from commit dadc7eb329)
2019-02-26 18:12:01 -05:00
..
androidndk-pkgs
arduino
beam-modules Merge pull request #25655 from elitak/beam 2019-02-25 10:22:51 -08:00
bower-modules/generic
compilers treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
coq-modules
dhall-modules
dotnet-modules/patches
em-modules/generic
go-modules
guile-modules
haskell-modules haskell-base-compat-batteries: fix build with ghc 8.2.2 and 8.4.4 2019-02-24 10:14:29 +01:00
idris-modules
interpreters
java-modules
libraries treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
lisp-modules
lua-modules
misc treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
mobile
node-packages
ocaml-modules
perl-modules
pharo treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
pure-modules
python-modules treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
r-modules
ruby-modules gem-config: add native taglib dependency to taglib-ruby gem 2019-02-25 12:20:52 +00:00
tools treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
web treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00