nodejs: Add update script

[adisbladis]

Motivation for this change

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Fits CONTRIBUTING.md.

---

Made https://github.com/NixOS/nixpkgs/pull/35118/files with the scripts in this PR.

cc nodejs maintainers @goibhniu @Havvy @gilligan @cko

[GrahamcOfBorg]

Success on x86_64-darwin (full log)

Partial log (click to expand)

/nix/store/06302fw8ik0nai9asn1zga64g88c2ifc-nodejs-6.12.3

[GrahamcOfBorg]

Success on x86_64-linux (full log)

Partial log (click to expand)

/nix/store/0qp6kmkrx0mqyqrfj781yw3kp2wbkf7y-nodejs-6.12.3

[gilligan]

I’m not sure I’m liking this much. Are we soon going to have hundreds of individual custom setups like this?

If at least the update logic was separate from the derivation itself, but right now that is not the case.

Bumping up a nodejs version is a matter of changing only a few lines and adjusting the sha. I don’t think the extra logic this PR introduces is worth it TBH.

[GrahamcOfBorg]

Success on aarch64-linux (full log)

Partial log (click to expand)

these paths will be fetched (6.70 MiB download, 32.58 MiB unpacked):
  /nix/store/g2pg448750pf27js1p5niwv831j973wv-nodejs-6.12.3
copying path '/nix/store/g2pg448750pf27js1p5niwv831j973wv-nodejs-6.12.3' from 'https://cache.nixos.org'...
/nix/store/g2pg448750pf27js1p5niwv831j973wv-nodejs-6.12.3

[adisbladis]

@gilligan This allows for updating packages using the maintainers scripts found in maintainers/scripts/update.nix.
Using that I don't necessarily have to keep track of upstream updates.

[gilligan]

@adisbladis Yes, i get that. It’s just that i find the added boilerplate scripting going on pretty “meh”.

Is that really the approach for all packages in the future?

[adisbladis]

I guess most packages would be able to use a more generic update mechanism as described #33848.
Actually come to think of it updateScript should probably be an attribute of the src.

[Havvy]

@adisbladis Could you remove me from the maintainer's list? I've not been maintaining this for a long time now.

[adisbladis]

@Havvy Done in e0c82dc