On Mon, Jan 9, 2023 at 3:25 PM Maxwell G via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > Jan 7, 2023 4:41:29 PM Lumír Balhar <lbalhar@xxxxxxxxxx>: > > > y-py upstream uses maturin as a build backend which is not available in > > Fedora yet so I had to add some metadata manually to port it to > > setuptools-rust > Why not package maturin? Is there something particularly problematic > about maturin (e.g. lots of missing dependencies) or is it just lack of > time? Packaging maturin is on the long-term roadmap for the Rust SIG, but it's currently blocked for at least two reasons: - a few dozen dependencies are not packaged for Fedora yet - some of the dependencies which *are* packaged are too old in Fedora, but updating to newer versions is blocked by our tool's lack of support for newer cargo features - some of the dependencies / features of maturin will probably not be acceptable as Fedora packages, because they require accepting Microsoft EULA (I hope it will be possible to patch out / disable those features) - some of the dependencies / features of maturin are not available on all Fedora architectures (most notably, the zig compiler, and the rustls TLS backend) - I hope these features are optional for what we need to build RPM packages, but I haven't been able to confirm that yet Last time I looked into maturin, I tried to document the current state of things here: https://copr.fedorainfracloud.org/coprs/decathorpe/maturin/ I haven't had time to look into this further since. So the easiest solution for y-py was to port it from maturin to setuptools_rust, which is already packaged for Fedora, and has already been used successfully for building Python packages for a while. Most of the additional features that maturin provides compared to setuptools_rust are only useful for upstream development, so until maturin is available as a Fedora package, porting projects to setuptools_rust is much easier than waiting for maturin to be packaged. Fabio _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue