https://bugzilla.redhat.com/show_bug.cgi?id=1853087 --- Comment #4 from John Baublitz <jbaublitz@xxxxxxxxxx> --- Hi Robert-André, this makes a lot more sense. Thank you for the clarification. I'll make the requested changes to the spec file as well. I just have one last question for future reference. The addition of this package is to support building a Rust application that takes advantage of libcryptsetup functionality. While it makes sense that the devel package for the bindings should require libcryptsetup-devel to be installed if this package is installed, should the runtime dependency on libcryptsetup be handled by the application I mentioned? I've dealt with Rust builds outside of Fedora packaging quite a lot and there's not really a good way to ensure through cargo that external dependencies are installed for bindings to execute properly and so the best you can usually do is check that a runtime application is installed in the application code because, like you mentioned, only static linking is supported at the crate level. However, with Fedora packaging there's a way to enforce non-Rust dependencies. Does that responsibility fall on the application RPM to enforce? I can't imagine there's a way to enforce this from a library as these RPMs seem to only be used in service of building a final application executable from the documents I've read. -- 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 _______________________________________________ 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
