> It would be nice of you if you compared your work and their work. Trying compare google/gyp and nodejs/node-gyp (and node gyp)...
$ git clone https://chromium.googlesource.com/external/gyp $ (cd gyp; git rev-parse HEAD) caa60026e223fc501e8b337fd5086ece4028b1c6 $ git clone https://github.com/nodejs/node-gyp.git $ (cd node-gyp; git rev-parse HEAD) 741ab096d554f2d3e6b6a7232b06872a0c1375f8 $ diff -ruN -x test -x .git gyp/ node-gyp/gyp/ | grep "^diff" | wc -l 50 $ diff -ruN {,node-gyp/}gyp/pylib/ | grep "^diff" | wc -l 32 At top level diffs exclude pylib directory: - setup.py, gyp, gyp.bat => no diffs - gyptest.py => gyp only - gyp_main.py => node-gyp add code for cygwin - buildbot/, test/ => gyp only - data/ => no diffs - samples/ => node-gyp doesn't support py3 https://chromium.googlesource.com/external/gyp/+/bd11dd1c51ef17592384df927c47023071639f96%5E%21/#F7 - tools/ => no diffs about python 3 support - tools/pretty_gyp.py => node-gyp doesn't import following patch (but not related py3 support) https://chromium.googlesource.com/external/gyp/+/5874a3cf9baccfae5cbfc4f5b84ba9a5c3568133%5E%21/#F0 - tools/pretty_sln.py => minor changes - tools/pretty_vcproj.py => minor changes and py3 support node-gyp has original patch, but it's the same as gyp, semantically. https://github.com/nodejs/node-gyp/pull/1793 (to be continued...) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel