Skip to content

build: enable xz compressed tarballs where possible (v0.12 and v0.10)

Rodrigo Muino Tomonari requested to merge github/fork/rvagg/xz-all-the-things into v0.12-staging

Continuing on from https://github.com/nodejs/build/issues/284

/cc @chorrell, @mscdex, @ljharb, @nodejs/build

We didn't actually agree on anything there but I'm in a why not mood right now.

This will mean that we get .xz tarballs from v0.12.10 and v0.10.42 onwards for those lines. Backing up and providing .xz tarballs for the others is impossible unless we exclude them from the signed SHASUMS file, which is far from ideal so I'm a strong -1 on completing v0.12 and v0.10. Tools like nvm will just have to hardwire in versions numbers for determining when to use .xz and when to use .gz. We're going to have to do something similar in node-gyp to use header files for older versions now that we have them fixed (the same versions will finally have a proper header tarball that can be used).

Merge request reports