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
..
build-runtime.py
build-wrapped.sh
chrootenv.nix	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
default.nix	steamcmd: init at 20180104	2018-09-08 13:39:32 -07:00
fonts.nix
runtime-generated.nix	run update_runtimes.py	2019-02-05 12:20:17 +01:00
runtime-mirror.nix
runtime-wrapped.nix	steamPackages.steam-runtime-wrapped: don't include all of gcc	2018-11-05 22:46:53 +00:00
runtime.nix
steam.nix	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
steamcmd.nix	steamcmd: init at 20180104	2018-09-08 13:39:32 -07:00
steamcmd.sh	steamcmd: init at 20180104	2018-09-08 13:39:32 -07:00
update-runtime-shell.nix
update-runtime.py	steam: made update-runtime.py nicer	2018-10-25 10:33:37 +02:00