-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-vendor node/node-gyp --> tools/gyp/ #28555
Comments
I'm not involved in gyp maintenance, so no comment on whether we should do this (though python3 support is clearly something we want). But in terms of how, look at 3a334b1 as an example, expecially of the commit message, and you can just @nodejs/gyp |
We were (are?) floating patches on top of gyp. I think these have been ported across to node-gyp (nodejs/node-gyp#1518) but it’s something we need to watch out for (e.g. nodejs/node-gyp#1661 had to address one case where the relative directory structure differs between node-gyp and here). |
node-gyp !== gyp. We’d only want to vendor the gyp part of the node-gyp repository (in the absence of a more official maintained upstream gyp source). |
This all seems to be done. nodejs/node-gyp#1791 would still be a huge leap forward. |
Perhaps we should be vendoring gyp3 in? #26620 would be an attempt at that. |
As discussed at #28537 (comment), in order to keep advancing towards Python 3 compatibility, we should re-vendor the repo node/node-gyp --> this repo's tools/gyp/ directory.
What is the best approach for vendoring in?
Is your feature request related to a problem? Please describe.
Please describe the problem you are trying to solve.
Node.js does not yet build on Python 3 and Python 2 EOL is in < 6 months.
Describe the solution you'd like
Please describe the desired behavior.
Node.js builds on Python 3.
Describe alternatives you've considered
Please describe alternative solutions or features you have considered.
Going kitesurfing.
The text was updated successfully, but these errors were encountered: