https://bugzilla.redhat.com/show_bug.cgi?id=2264463
--- Comment #8 from Ben Beasley code@musicinmybrain.net --- Hmm, I suppose we could simply do
%pyproject_install rm -rv %{buildroot}%{python3_sitearch}/cramjam_cli-%{version}.dist-info
Or, it turns out it is possible to build and install this with %cargo_build/%cargo_install instead of %pyproject_wheel/%pyproject_install, which would prevent the Python metadata from being generated in the first place.
I still need the Python BuildRequires to run the tests, and I still need to package from the PyPI sdist because cramjam-cli is not published on crates.io and the commits corresponding its releases are not currently explicitly tagged in the GitHub repository.
Still, maybe one of the above approaches is the way to go. Anything that currently tries to depend on cramjam-cli as a Python package and then call the command-line tool via subprocess or similar would need patching, but that’s already the status quo for some other other attempts to hackily deliver executables via PyPI (https://pypi.org/project/cmake/, https://pypi.org/project/ninja/). Why, and whether, anything would do that when https://pypi.org/project/cramjam/ is available is another question.
I’ll let this sit as-is for the moment and possibly revise it a little later.