-
Notifications
You must be signed in to change notification settings - Fork 73
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
Claim "gyp" on PyPI #3
Comments
"gyp-next" is not taken. can we close this issue? |
It would be cool to get |
@cclauss I got gyp-next, so we're good there. IDK if we need gyp tbqh, but we can talk to Chromium Authors for a handoff (they'd probably be happy to). Do you both agree we should proceed? |
I believe that we should grab both. Otherwise we are going to have to answer the same support questions over and over again. |
We have been using gyp-next for a while. Should we continue to seek gyp on pypi? If not, maybe we can close this. |
I don't think it's going to be worth the effort. |
If you can get the owners and/or PyPI to give us that domain, then we will take it. |
"gyp" is taken on PyPI (https://pypi.org/project/gyp/). I guess it would make sense to contact the uploader/Chromium folks/Google OSPO about this.
/cc @cclauss
The text was updated successfully, but these errors were encountered: