qbit/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
c8ff4a92f7
nixpkgs/pkgs
History
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
..
applications treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
build-support treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
common-updater
data creep: init at 0.31 (#56264) 2019-02-25 11:12:54 -06:00
desktops treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
development treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
games treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
misc treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
os-specific treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
servers treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
shells Merge pull request #56173 from worldofpeace/worldofpeace-updates 2019-02-22 12:54:36 -05:00
stdenv
test
tools treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00
top-level treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 18:12:01 -05:00