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
..
csslint	treewide: http -> https sources (#42676)	2018-06-28 20:43:35 +02:00
grails	grails: 3.3.8 -> 3.3.9	2019-01-02 21:33:37 +01:00
insomnia	insomnia: 6.2.3 -> 6.3.2	2019-01-03 09:14:59 -08:00
kcgi	kcgi: 0.10.7 -> 0.10.8	2019-01-13 09:49:48 +01:00
kore	kore: fix clang build	2018-03-20 00:00:42 +01:00
mailcatcher	mailcatcher: rack: 1.6.8 -> 1.6.11	2018-11-06 09:23:20 +00:00
minify	pkgs/*: remove unreferenced function arguments	2018-07-21 02:48:04 +00:00
nodejs	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
now-cli	now-cli: 13.0.4 -> 13.1.2	2019-01-27 23:46:17 -08:00
postman	postman: 6.7.1 -> 6.7.3	2019-02-11 23:08:43 +01:00
remarkjs	reewide: Purge all uses stdenv.system and top-level system	2018-08-30 17:20:32 -04:00
twitter-bootstrap	twitterBootstrap: v2 -> v3	2018-08-28 12:52:13 +01:00
valum	valum: 0.3.14 -> 0.3.15	2018-03-09 15:52:32 -08:00
wml	lib.makePerlPath -> perlPackages.makePerlPath	2018-12-15 03:50:31 +00:00
woff2	woff2: supports darwin	2018-05-31 12:34:15 -04:00
xmlindent