> Batching is now the default, but maintainers can push theirs updates > to stable, overriding this default, and make the update available the > next day. I think that since "batch override" doesn't push the package immediately, but rather schedules it for the next day, I agree with Fabio that it might be a good idea to flush the "batch queue" when a package is explicitly pushed to stable by someone. This won't increase the number of metadata expirations - so there isn't really any drawback to end users - while allowing updates to reach users faster. > + batching reduces the number of times repository metadata is updated. > Each metadata update results in dnf downloading about 20-40 mb, > which is expensive and/or slow for users with low bandwidth. As someone with a rather small data cap, I'd say that heavy metadata downloads during "dnf update" are acceptable - since I can just choose to run "dnf update" only once a week or so. But it always irks me a bit when I want to install a new package and dnf starts downloading the repository metadata again. Bandwidth issues aside, it's just incredibly annoying having to wait for a 40MiB download to complete before I can fetch a single 600KiB package. > - batching delays updates of packages between 0 and 7 days after > they have reached karma and makes it hard for people to immediately > install updates when they graduate from testing. I agree with Jerry here - many packages don't get any karma while testing. The only time my packages received testing karma was when I was introducing new packages; didn't happen for updates. So having the package sit in limbo for another week after going through a week of "maybe someone'll take a look at this" is a bit discouraging. > One of the positive aspects of batching — reduction in metadata downloads, > might be obsoleted by improving download efficiency through delta downloads. > A proof-of-concept has been implemented [4]. This could be a rather interesting feature, as it'd resolve some of the issues I wrote two paragraphs above. By the way - does drpm handling depend on repo / mirror settings? I ask because I'm under the impression that lately hardly any package update on my system is done via delta-RPMs; it's about 1-in-100 or so. Is this more a matter of me needing to tweak dnf config, or can this depend on the package mirrors? A.I. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
