Vít Ondruch kirjoitti 24.9.2021 klo 11.13:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#multiple_packages
Shouldn't it be somehow aligned with this ^^ chapter? Maybe the chapter
should be referenced at least, because it explains how to request the
side tag.
The difference between these two sections is that one is under "Rawhide
and early branched", the other "Later Branched and stable releases".
Currently, one prescribes a side tag and the other, a buildroot
override. Probably one could just refer to the other, or both refer to
another place.
Pointing to the Rawhide Gating page for instructions is fine, but I
wonder would it actually be better to do it the other way, describe the
process correctly in Package Maintainer Docs and link there from the
Rawhide Gating page, which, judging from its title, has quite narrow scope.
There is also the page "Using the Koji build system" [1] which
recommends yet another solution: section "Chained builds". What about
those, what are they useful for?
Otto
[1]:
https://docs.fedoraproject.org/en-US/package-maintainers/Using_the_Koji_Build_System/
Dne 23. 09. 21 v 11:29 Miro Hrončok napsal(a):
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#updating_inter_dependent_packages
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?
_______________________________________________
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 on the list, report it:
https://pagure.io/fedora-infrastructure
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
