Some of the libuv buildbots seem to use a... bespoke?... copy of gyp:
https://ci.nodejs.org/job/libuv-test-commit-osx/1748/nodes=osx1011/console
+ mkdir build/gyp
+ curl -s http://ci.nodejs.org/downloads/zos/gyp.tar.gz
+ tar xvf - -C build/gyp/
$ curl -q --head http://ci.nodejs.org/downloads/zos/gyp.tar.gz | grep Last-Modified
Last-Modified: Wed, 27 Sep 2017 21:43:14 GMT
Does anyone know/remember why things are set up this way? I was thinking of extracting node's tools/gyp to https://github.com/libuv/gyp (so people can still build with a somewhat maintained version of gyp) and then switch over the CI to use that.
(Libuv's readme currently points people to chromium's obsolete copy of gyp.)
Some of the libuv buildbots seem to use a... bespoke?... copy of gyp:
https://ci.nodejs.org/job/libuv-test-commit-osx/1748/nodes=osx1011/console
Does anyone know/remember why things are set up this way? I was thinking of extracting node's tools/gyp to https://github.com/libuv/gyp (so people can still build with a somewhat maintained version of gyp) and then switch over the CI to use that.
(Libuv's readme currently points people to chromium's obsolete copy of gyp.)