https://bugzilla.redhat.com/show_bug.cgi?id=2316282
--- Comment #25 from Cristian Le <[email protected]> --- The libraries may be a drop in replacement, but the provides issue is a bit different. Consider if there is a package `foo.spec` which has the line ``` BuildRequires: pkgconfig(SvtAv1Enc) ``` Then which project would it be built against. Similarly in that `foo.spec` you do not specify a `Requires` because that is automatically detected from checking the linkages of the binary and libraries, but then which package will it automatically populate the `Requires` field with? I know there are examples with binary packages like different versions of `mariadb` and there was a talk on that design in the last devconf.cz, but for the library case and something that will be injected in `BuildRequires` I don't know what are the implications. I do not have enough experience with this issue so we should get more feedback on this issue and what needs to be done. -- 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=2316282 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202316282%23c25 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
