On 04/07/2017 05:40 PM, Adam Williamson wrote:
On Fri, 2017-04-07 at 10:32 -0400, Matthew Miller wrote:
On Fri, Apr 07, 2017 at 02:29:02PM -0000, Farhad Mohammadi Majd wrote:
I had firefox-52.0-6.fc25 and there was no Delta RPM for firefox-52.0.2-2.fc25
Does Delta RPM is available only for the installed recent version?
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.
Isn't that a wrong design decision by GNOME then? With respect to
Firefox we are often talking about security fixes which should not be
delayed anyway. I get the point of not bothering the user all day, but
security is a special case for me. I don't have a statistics on how
often we have security fixes in stable releases, maybe there could be
something like "if we have security fix => notifiy user now, otherwise
wait until next regular update time"
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
