New comment by eli-schwartz on void-packages repository

https://github.com/void-linux/void-packages/pull/40385#issuecomment-1307756725

Comment:
> The flit build style doesn't help us here because we would still need something to install wheels. That means that, except for `python3-build` and `python3-pyproject-hooks`, every other package added here will still need custom behavior.

Yeah, all two of them. :p To put it another way, you reduce the problem by 50%.

> We tend not to fetch prebuilt artifacts, so grabbing the wheel isn't really viable.

The official PyPA policy on that is "wheels are just source code copied into a different directory", which is... sort of kind of true, if you squint.

Simply hope and pray that you don't ever need to apply patches to it, as it then rapidly becomes a built artifact (where the patches are part of the input pipeline) as you cannot patch a wheel.

(Yes I know this isn't nearly as helpful as PyPA thinks. We've finally reached a nearly bootstrappable world where you only need to treat a single package as magic, or, depending, two packages. But they really want you to treat *something* as magic.)