Richard W.M. Jones wrote:
> Is there any reason why you _wouldn't_ want Bodhi to take an update
> automatically after a successful Koji build of a non-Rawhide package?
Grouped updates.
For example, a xulrunner security update can't just be pushed out as soon as
it's build, it requires building xulrunner, getting it tagged into the
buildroot, then building an updated firefox and rebuilding several other
xulrunner-using packages and then pushing everything as a grouped update.
Doing it any differently would break dependencies.
In some other cases, like KDE, it would be technically possible to push
first the libs, then each application module one by one, but this would be
much more chaotic than just pushing the new version out as a grouped update
as we're doing now. And people don't really test e.g.
kdebase-workspace-4.1.2 with kdelibs-4.1.3, it should work due to backwards
compatibility, but normally users are expected to update those modules to
4.1.3 together. And we need to support grouped updates anyway for the cases
where we don't have backwards compatibility, like xulrunner (for those apps
using the xulrunner-unstable interfaces, which include Firefox).
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
