nixpkgs/pkgs/development/tools/haskell
Jörg Thalheim dadc7eb329
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.
2019-02-26 14:10:49 +00:00
..
hyper-haskell treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 14:10:49 +00:00
ihaskell ihaskell: Do not unset $PATH in the wrapper 2018-06-08 16:32:59 +02:00
lambdabot pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
leksah leksah: mark as broken 2018-09-13 02:27:04 +02:00
mueval lambdabot: rework custom modules and configuration 2015-09-08 17:50:55 +03:00
multi-ghc-travis multi-ghc-travis: update to latest git version 2018-09-27 15:55:02 +02:00
vaultenv vaultenv: 0.5.3 -> 0.8.0 2018-09-12 11:44:22 +08:00