On Fri, Apr 7, 2017 at 9:44 AM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Apr 07, 2017 at 08:40:25AM -0700, Adam Williamson wrote: >> > We have delta RPMs for going from GA release packages to current >> > updates and from last update to current update. Doing deltas from all >> > previous updates to all future updates would become a crazy out of >> > control matrix very quickly. Generating deltarpms is already a >> > *gigantic* use of computing resources in the project, and extending >> > that just isn't reasonable unless you have a huge hardware donation up >> > your sleeve.... >> There is a bit of a problem with that, though, and packages that >> iterate quickly. 52.0-6 went stable on 2017-03-24. 52.0-7 went stable >> on 2017-03-30. 52.0.2-2 went stable on 2017-04-05. There isn't a week >> between any of those; given that (IIRC) GNOME is designed to notify >> users of updates only once a week, it's quite easy to *not* be going >> from 'latest minus 1' to 'latest' in this kind of scenario. > > Yeah, that's fair. I'm not sure of a really good solution for this > other than ostree-based flatpaks — and that has its own challenges. I think most of those challenges are on the Fedora side of things, infrastructure and packaging resources? I'd been running the nightly Firefox dev flatpak on Fedora 25 with exactly zero problems. Aren't flatpak updates something like a git pull? Anyway, they always seem fast, not matter if I updated daily or weekly. I'd guess the delta is file based rather than block based - or however RPM does it. That does consume a lot of resources on both the Fedora side as well as client side. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
