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
..
amazon-glacier-cmd-interface
bacula
bareos
bdsync
borg	borgbackup: 1.1.8 -> 1.1.9	2019-02-11 09:43:36 +01:00
btar
btrbk
bup
burp	burp: 2.2.16 -> 2.2.18 (#56288)	2019-02-24 17:17:18 +01:00
chunksync
dar	dar: 2.6.0 -> 2.6.1	2019-01-28 13:44:03 -08:00
ddar
dirvish	maintainer-list: add winpat	2019-02-10 16:19:38 +01:00
diskrsync
duplicati
duplicity
duply	duply: 2.1 -> 2.2	2019-01-29 07:27:40 +01:00
easysnap	easysnap: 2018-11-20 -> 2019-02-17	2019-02-17 13:08:51 +01:00
flockit	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
grab-site
httrack
lvmsync
mt-st
mtx
mydumper
ori
partclone
partimage
percona-xtrabackup
pyznap	pyznap: init at 1.1.2	2019-02-06 18:29:59 -05:00
rdedup	rdedup: mark as broken on darwin	2019-02-13 12:12:01 +02:00
rdiff-backup
rdup
restic	restic: 0.9.2 -> 0.9.4	2019-02-14 23:27:34 +01:00
rsbep
rsnapshot
s3ql
store-backup
tarsnap
tarsnapper
ugarit
ugarit-manifest-maker
wal-e
wal-g
zbackup
znapzend