Cristian Le

Beyond the `build-system`, my worry is if the python files gain more functionalities like https://github.com/scikit-build/cmake-python-distributions/issues/36 such that it is used beyond the building of python packages. > One other problem...

Ok, that's reassuring. Could the relevant feature requests be closed?

Also, maybe adding some notes/warning on the README such that people do not start using/relying on the python files here, and instead use other tools that check the availability of...

Indeed, on the backend `rpminspect` simply exports to `json` and the `viewer.html` simply reads it directly.

So with #1267 merged, what is needed to move this feature forward?

`cps_version` is also missing. Hint, on PyCharm, you can make `.cps` file be considered a json file, and then add the `_site/cps.schema.json` as its json schema to validate

Unfortunately that would be incompatible with PyPI packaging where including an optional-dependency does not add, change, or remove files being installed, only dependencies installed change. What you could do is...

I will run a build in Fedora, don't have access to the other environments (I'll post another reply with the rebuild link), but these should be fine and backwards-compatible

[Here](https://src.fedoraproject.org/rpms/airspyone_host/pull-request/3) it is building in Fedora (link inside for CMake 4.0 build as well)

Regarding the comment by @bvernoux, this is a genuine licensing concern which could impact distro packaging. Please have an issue to discuss this and we can raise an issue on...