nixpkgs/pkgs/os-specific/darwin/stubs/default.nix

{ stdenv, writeScriptBin, runtimeShell }:

let fake = name: stdenv.lib.overrideDerivation (writeScriptBin name ''
  #!${runtimeShell}
  echo >&2 "Faking call to ${name} with arguments:"
  echo >&2 "$@"
'') (drv: {
  name = "${name}-stub";
}); in

{
  setfile = fake "SetFile";
  rez = fake "Rez";
  derez = fake "DeRez";
}
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 12:45:54 +01:00			`{ stdenv, writeScriptBin, runtimeShell }:`
wxmac: clean up and provide with stub packages 2015-10-29 01:36:20 +01:00
			`let fake = name: stdenv.lib.overrideDerivation (writeScriptBin name ''`
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 12:45:54 +01:00			`#!${runtimeShell}`
wxmac: clean up and provide with stub packages 2015-10-29 01:36:20 +01:00			`echo >&2 "Faking call to ${name} with arguments:"`
			`echo >&2 "$@"`
			`'') (drv: {`
			`name = "${name}-stub";`
			`}); in`

			`{`
			`setfile = fake "SetFile";`
			`rez = fake "Rez";`
			`derez = fake "DeRez";`
			`}`