I posted a link to this thread in the Picard Development room on Matrix, so hopefully someone who understands the build process better than I do can give you some pointers. My go-to for stuff like that is @outsidecontext.
I assume the pyproject_wheel part is expecting a PEP 517 compatible build system? This makes building so much easier compared to the old way of calling setup.py, and Picard’s build is compatible with this. But depending on the builder being used it makes it more complicated or sometimes impossible to pass the custom parameters.
Maybe we need to rethink how we handle such build time options to be able to use them with any compatible builder (such as python -m build).
Thanks! I got a little closer, but still an error. After reading that I needed KEY=VALUE I tried the entry below and many variations but none worked. I’ll keep hacking at it, if you can think of anything else, let me know!
I would have expected something like python -m build --wheel -C--disable-autoupdate or maybe python -m build --wheel -C--disable-autoupdate=True should work, but it doesn’t for now, as the parameters are not passed on.
Thank you very much for taking the time to reply. So basically the functionality to pass arbitrary options isn’t working correctly or hasn’t been provisioned. I’m going to open a ticket with the Fedora Python folks and see what they recommend, if anything. I’ll report back here.
Edit: In the meantime, I’ll just patch setup.py as a work-around until this gets solved.