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
..
library	nixpkgs docs: document recursivelyUpdate	2018-10-12 16:54:34 -04:00
appimagetools.xml	appimageTools: init	2019-02-23 21:04:21 +01:00
debug.xml	nixpkgs docs: Reformat	2018-10-02 15:59:59 -04:00
dockertools.xml	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
fetchers.xml	nixpkgs/manual: address review comments	2019-01-27 11:57:36 -05:00
fhs-environments.xml	nixpkgs docs: Reformat	2018-10-02 15:59:59 -04:00
generators.xml	nixpkgs docs: Reformat	2018-10-02 15:59:59 -04:00
library.xml	doc: Add automatic generation of library function documentation	2019-01-04 11:28:27 +01:00
nix-gitignore.xml	nix-gitignore: init at v3.0.0 (#46112)	2019-02-18 09:57:30 +00:00
overrides.xml	Merge pull request #47430 from roberth/nixpkgs-extend	2018-10-23 20:21:48 -04:00
prefer-remote-fetch.xml	prefer-fetch-remote: an overlay to fetch on remote builders	2019-01-18 14:41:10 +00:00
shell.xml	nixpkgs docs: Reformat	2018-10-02 15:59:59 -04:00
trivial-builders.xml	nixpkgs/manual: add one more fix for a missed review	2019-01-27 12:01:23 -05:00