On Tue, 2022-11-22 at 12:48 +0100, Vít Ondruch wrote: > > Would it be possible to develop a way to better manage updates of some > interconnected packages? FF + NSS would be one case, but when we are > doing Ruby on Rails update, it always involve more packages. Or probably > gcc + annobin are pair of packages which needs to always go together > (unless I am mistaken). > > E.g. the build of NSS would automatically triggered side creation and > waited for updated FF. well...there's always room for improvement, but it strikes me that would be rather complicated. It's not the case that *every* rebuild of NSS requires a rebuild of Firefox, so whatever is implementing this would need to be quite smart to know when it's necessary and when it isn't. Frankly, the existing tools are fine for the purpose. It is not hard to create a side tag, nor to put builds in it. Multiple other maintainers and teams manage this just fine, with much larger sets of packages: the desktop and KDE teams both do this very well, all the time, with dozens of packages. Bluntly, I don't think there is really a tooling problem here, there is a "getting the maintainers to understand the requirements and use the tooling properly" problem. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ 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
