nixpkgs/pkgs/development/web/nodejs/update.nix

{ stdenv
, lib
, writeScript
, coreutils
, curl
, gnugrep
, jq
, gnupg
, common-updater-scripts
, majorVersion
, nix
, runtimeShell
}:

writeScript "update-nodejs" ''
  #!${runtimeShell}
  PATH=${lib.makeBinPath [ common-updater-scripts coreutils curl gnugrep jq gnupg nix ]}

  HOME=`mktemp -d`
  cat ${./nodejs-release-keys.asc} | gpg --import

  tags=`curl --silent https://api.github.com/repos/nodejs/node/git/refs/tags`
  version=`echo $tags | jq -r '.[] | select(.ref | startswith("refs/tags/v${majorVersion}")) | .ref' | sort --version-sort  | tail -1 | grep -oP "^refs/tags/v\K.*"`

  curl --silent -o $HOME/SHASUMS256.txt.asc https://nodejs.org/dist/v''${version}/SHASUMS256.txt.asc
  hash_hex=`gpgv --keyring=$HOME/.gnupg/pubring.kbx --output - $HOME/SHASUMS256.txt.asc | grep -oP "^([0-9a-f]{64})(?=\s+node-v''${version}.tar.xz$)"`
  hash=`nix-hash --type sha256 --to-base32 ''${hash_hex}`

  update-source-version nodejs-${majorVersion}_x "''${version}" "''${hash}"
''
update.nix: Run update scripts in parallel To make updating large attribute sets faster, the update scripts are now run in parallel. Please note the following changes in semantics: - The string passed to updateScript needs to be a path to an executable file. - The updateScript can also be a list: the tail elements will then be passed to the head as command line arguments. 2018-11-23 17:03:19 +00:00			`{ stdenv`
			`, lib`
nodejs: Add updater script 2018-02-18 14:19:01 +00:00			`, writeScript`
			`, coreutils`
			`, curl`
			`, gnugrep`
			`, jq`
			`, gnupg`
			`, common-updater-scripts`
			`, majorVersion`
			`, nix`
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 11:45:54 +00:00			`, runtimeShell`
nodejs: Add updater script 2018-02-18 14:19:01 +00:00			`}:`

			`writeScript "update-nodejs" ''`
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 11:45:54 +00:00			`#!${runtimeShell}`
nodejs: Add updater script 2018-02-18 14:19:01 +00:00			`PATH=${lib.makeBinPath [ common-updater-scripts coreutils curl gnugrep jq gnupg nix ]}`

			HOME=`mktemp -d`
			`cat ${./nodejs-release-keys.asc} \| gpg --import`

			tags=`curl --silent https://api.github.com/repos/nodejs/node/git/refs/tags`
			version=`echo $tags \| jq -r '.[] \| select(.ref \| startswith("refs/tags/v${majorVersion}")) \| .ref' \| sort --version-sort \| tail -1 \| grep -oP "^refs/tags/v\K.*"`

			`curl --silent -o $HOME/SHASUMS256.txt.asc https://nodejs.org/dist/v''${version}/SHASUMS256.txt.asc`
			hash_hex=`gpgv --keyring=$HOME/.gnupg/pubring.kbx --output - $HOME/SHASUMS256.txt.asc \| grep -oP "^([0-9a-f]{64})(?=\s+node-v''${version}.tar.xz$)"`
			hash=`nix-hash --type sha256 --to-base32 ''${hash_hex}`

			`update-source-version nodejs-${majorVersion}_x "''${version}" "''${hash}"`
			`''`