Il 22/01/24 19:39, blinxen ha scritto: > > I am unaware of any remaining use cases for buildroot overrides that > are not covered by side tags > > One use case that I sometimes encounter is requiring a newer version for > a dependency, > that is submitted to Bodhi with a side-tag. Since the build is in a > side-tag, I can't access it > without building into that specific side-tag. Also I can't stop the > Bodhi Update just to add my own > build. In this case, I need to create a buildroot override to be able to > build my package in my own side-tag. > > Sure, I can wait a couple of days for the update to land in stable but > it's nice that I can also have a > on-demand buildroot override that can speed things up. > -- IMO, that's the perfect example of how buildroot overrides must NOT be used... Say libfoo-1.0 is in a side-tag update. You use a BRO to build another package, or, maybe worse, someone who is not aware of the BRO you created build their package against libfoo-1.0, and those packages are submitted in different updates. If, for some reason, libfoo-1.0 update lands in stable after the other packages, or never lands because it is gated or is blocked by negative feedback, the other packages are getting broken when they're submitted to stable. The purpose of side-tags is exactly to prevent such breakages. Mattia -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
