https://bugzilla.redhat.com/show_bug.cgi?id=2186844 --- Comment #4 from blinxen <h-k-81@xxxxxxxxxxx> --- > Yes, the patch is there to make it easier to choose the crypto backend for building this crate, running tests against different backends, and for dependent packages to be able to choose a backend independently I forgot to ask the following: ``` %cargo_generate_buildrequires -f crypto-nettle,crypto-openssl %build %cargo_build -f crypto-nettle %install %cargo_install -f crypto-nettle %if %{with check} %check # run tests with both cryptographic backends %cargo_test -f crypto-nettle %cargo_test -f crypto-openssl %endif ``` The `cargo_generate_buildrequires` macro includes both backends, the `check` section tests for both backends but the `build` and `install` section uses the `crypto-nettle` backend. Is this intended? -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2186844 _______________________________________________ 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
