Repository navigation
request to move the refack/GYP repo to the org #247
Description
It seems the remaining support Google was providing for GYP has ended (CI doesn't work anymore, and the last contributor is not responding), so I request to move a forked repo to the org.
This will facilitate current efforts to make GYP python3 compatible (nodejs/node-gyp#1335, nodejs/node-gyp#1150, nodejs/node#23669, gyp-developer/ivg8pfDSrr0), as well as bug fixes and adaptation to new toolchain versions. Most importantly I want to revive GYP's CI test suite so we could have decent coverage of our current and future floating patches.
My assumption is that first and foremost this will help alleviate node-gyp pain points. Following that I have several ideas for improvements:
- automating GYP-GN cross-compatibility
- static analysis and debugging tools to
.gypfiles (make it easier to maintain) - build time optimizations (such as whole library caching, since only tools at this level have knowledge of all the inputs and variables used when building a library as a whole)
- adapting to new features in existing toolchains.
IMHO coordinating such efforts requires the umbrella of an organization such ours, since bootstrapping a personal fork (especially one that is diverging from Google, and not explicitly affiliated with Node.js) is very challenging.
/CC @nodejs/gyp @node-gyp @nodejs/build @nodejs/build-files @nodejs/python
Activity
joaocgreis commentedon Oct 18, 2018
Link: https://github.com/refack/GYP
This sounds good to me. Ideally, I'd like to see node-gyp move to gyp.js, thus not requiring Python at all. I realize that this will require some more work, so for now being able to easily fix issues in gyp would be great.
joyeecheung commentedon Oct 19, 2018
SGTM. Until we make a decision on the build system we want to switch to (or even if we want to switch to a new one), the current status is that we will have to maintain a fork of GYP anyways.
Also, thanks for all the work you put into maintaining the GYP stuff!
jasnell commentedon Oct 19, 2018
Sgtm
mcollina commentedon Oct 19, 2018
targos commentedon Oct 19, 2018
Sgtm
mhdawson commentedon Oct 19, 2018
Sgtm
richardlau commentedon Nov 1, 2018
This can go ahead. as per https://github.com/nodejs/admin/blob/master/GITHUB_ORG_MANGEMENT_POLICY.md#repositories
refack commentedon Nov 1, 2018
Thanks, I'm setting things up, and will try to follow up in the next few days.
Croydon commentedon Jun 20, 2019
What happened to this? 🤔
sinloss commentedon Jun 27, 2019
What happened? +1