Commit Graph

8 Commits

Author SHA1 Message Date
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
rnhmjoj
bcf54ce5bb
treewide: use ${stdenv.shell} instead of /bin/sh where possible 2019-01-16 20:37:15 +01:00
ndowens
98b9b07a98 alchemy: 007 -> 008 2017-03-18 16:38:41 -05:00
Eelco Dolstra
40f7b0f9df Another attempt to eradicate ensureDir
See c556a6ea46.
2014-06-30 14:56:10 +02:00
Bjørn Forsman
a14365b568 alchemy: add meta.longDescription 2014-06-22 21:46:34 +02:00
Evgeny Egorochkin
d3f53cdde4 alchemy: fix version to match tarball 2013-07-14 02:08:55 +03:00
Marc Weber
67d41e4424 gpl fix 2013-05-30 01:30:48 +02:00
Marc Weber
af4d6b73de adding alchemy painting application 2013-05-22 22:58:05 +02:00