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
..
1.4.nix	treewide: remove wkennington as maintainer	2019-01-26 10:05:32 +00:00
1.10.nix	go_1_10: fix tests after binutils update	2019-02-19 11:35:54 +01:00
1.11.nix	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
creds-test-1.4.patch
creds-test.patch
go-1.9-skip-flaky-19608.patch
go-1.9-skip-flaky-20072.patch
remove-fhs-test-references.patch	go_1_11: init at 1.11	2018-08-26 23:11:10 +08:00
remove-test-pie.patch
remove-tools-1.4.patch
remove-tools-1.9.patch
remove-tools-1.11.patch	go_1_11: init at 1.11	2018-08-26 23:11:10 +08:00
setup-hook.sh
skip-external-network-tests.patch	go_1_11: init at 1.11	2018-08-26 23:11:10 +08:00
skip-nohup-tests.patch	go_1_11: init at 1.11	2018-08-26 23:11:10 +08:00
skip-test-extra-files-on-386.patch	go: skip flaky os/exec TestExtraFiles	2018-09-15 18:46:18 +02:00
ssl-cert-file-1.9.patch