https://bugzilla.redhat.com/show_bug.cgi?id=2241062 --- Comment #8 from Christoph Erhardt <fedora@xxxxxxxxxxx> --- Link to bug report added to `.spec` file. I'm a bit undecided when it comes to the SONAME topic. Can semantic versioning even be applied properly when two independent libraries - one in Rust, one in C - are hosted within the same Git repository? For instance, an interface-breaking change in the Rust code would have to trigger a new major version (and thus a new SONAME) even if the C interface remains the same. That would mean unnecessary extra packaging effort for downstream distributions. Right now I'm leaning slightly towards the 'increment whenever the ABI breaks' approach. For a simple cryptographic-hash library such as blake3 I don't expect frequent interface changes anyway. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2241062 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202241062%23c8 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue