why doesn't gyp-pyxx provide gyp???

[TheSin-]

gyp is a build tool, so why won't gyp-pyxx provide gyp for build depends?? packages using it likely won't depend on it (if they do they should use the right py variant) but if a package just uses it as a builddepend why would they python version lock it??

can we add a provides to make it easier for other packages that just need it as a BD to use it?

[dhomeier]

Related: #993 (comment)
I have not found any indication of a package that would need gyp at runtime, but I also have no proof of that...

[TheSin-]

well in my case it will, cause it's a build tool that uses gyp at runtime (during builds). Why would I pick a python version for them, that's insane, I should be able to just dep on gyp

[TheSin-]

Any update here? this is a road block for me and I'm waiting.

[dhomeier]

I was rather thinking of package that import from gyp in their python code; but you are right that if all a package needs is a working %p/bin/gyp, then any of the variants provide it. So if I understand your case correctly, you could have it just
Depends: pip-py310 | pip-py39 | pip-py27
One could add a new convenience package analogously to mercurial.info to take care of this of course.
That would probably still not guarantee that things actually run with any gyp, since there are lots of old gyp build configs that will only every work with the py27 variant, and possibly some newer ones that are using py3x syntax.