https://bugzilla.redhat.com/show_bug.cgi?id=2295820 Jeremy Newton <alexjnewt@xxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexjnewt@xxxxxxxxxxxx --- Comment #3 from Jeremy Newton <alexjnewt@xxxxxxxxxxxx> --- So some more information from a ROCm developer, we were in a meeting that included Tom and me: The bundled tensile is a fork, and is expected to diverge from tensile (if it hasn't already) and become a replacement for tensile in rocm (other libs are supposed to eventually call rocblaslt). I'd rather just move forward, and we can drop tensile later if need be. > How do we handle the "bundled" tensile ... I don't think that it needs to be added to the provides but I also don't know if there is anything preventing this from happening A bundle is a bundle, you need to add it regardless. The provides is more of a flag. I believe the intention is if they a security issue or similar critical issue in the library, the maintainer can look for the provides to notify the other maintainer that there's a critical bug that needs fixing. This could also be a CVE, a license issue, a copyright issue, a legal issue, etc. Providing a version is pretty important too for tracking. E.g. say library A has a CVE and package B bundles A, then it's easy to query for "provides: A" to see what packages need updating, which would be A and B. -- 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=2295820 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202295820%23c3 -- _______________________________________________ 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
