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
..
ant-build.nix	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
binary-tarball.nix	treewide: random cleanups	2018-08-10 12:56:31 +00:00
debian-build.nix	debBuild: install all packages at once to avoid dependency management	2018-02-19 16:07:40 +03:00
default.nix	releaseTools: add channel function	2016-09-27 08:51:28 +09:00
functions.sh	stdenv/build-support: support .tbz and .txz tarballs	2018-07-30 15:30:16 -04:00
gcov-report.nix
maven-build.nix	USe maven.test.skip in stead of maven.test.skip.exec in mvn assembly, to prevent unnecessary compilation.	2014-05-07 16:37:38 +02:00
nix-build.nix	reewide: Purge all uses stdenv.system and top-level system	2018-08-30 17:20:32 -04:00
rpm-build.nix	findTarball: Handle pipefail	2014-11-05 18:24:16 +01:00
source-tarball.nix	schedulingPriority should be an int, fix check-meta type and in-tree use	2018-01-09 07:25:24 -06:00