I logged an issue about this for the Package Maintainer Docs [1]. Similarly to all other other issues in that list, I intend to do something about this at some point, unless somebody else beats me to it.
[1]: https://pagure.io/fedora-docs/package-maintainer-docs/issue/33
Otto
Miro HronĨok kirjoitti 23.9.2021 klo 12.29:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guid...
Says:
""" You may need a buildroot override to complete a multi-package update successfully. For instance in the case described above, you may need to rebuild bar against the new libfoo package and submit both packages together as a multi-package update. However, in the normal course of events, you would not be able to build another package against your new libfoo build until it reached the stable state. To resolve this dilemma, you can request a buildroot override, which causes the libfoo build to be included in the buildroot for a short time in order to get the bar package build done. """
However, I think side-tags should be the preferred solution, as their impact is isolated. Buildroot overrides create temporary broken dependencies for everybody, while side-tags don't.
My understanding was that this is the de-facto consensus, so I'd lie to update the docs to say something like:
""" You may need to build the inter-dependent packages in a side tag. For instance in the case described above, you may need to rebuild bar against the new libfoo package and submit both packages together as a multi-package update. However, in the normal course of events, you would not be able to build another package against your new libfoo build until it reached the stable state. To resolve this dilemma, you can request a side tag and build both packages in it, which causes the libfoo build to be included in the bar build's buildroot. """
And than instead of describing the details, link to https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/
Any suggestions or objections?