nixpkgs/pkgs/development/tools/build-managers/bazel
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
..
bazel-deps bazel-deps: 2018-11-01 -> 2019-02-01 2019-02-01 17:30:36 +11:00
buildtools bazel-buildtools: upgrade to 2018-10-11 (#48243) 2018-10-14 17:08:33 +02:00
0.4.nix bazel_0_4: mark as broken 2018-08-07 16:53:36 +02:00
bash-tools-test.nix Add test and docs. 2019-01-26 22:22:34 +01:00
default.nix treewide: use runtimeShell instead of stdenv.shell whenever possible 2019-02-26 14:10:49 +00:00
nix-hacks-0.4.patch bazel: Bump nix-hacks.patch for 0.9. 2018-01-18 10:25:47 -05:00
nix-hacks.patch bazel: Bump nix-hacks.patch for 0.9. 2018-01-18 10:25:47 -05:00
python-bin-path-test.nix Add test and docs. 2019-01-26 22:22:34 +01:00
python-stub-path-fix.patch bazel: fix python stub paths. 2019-01-15 19:25:24 +01:00