https://bugs.kde.org/show_bug.cgi?id=433587

--- Comment #11 from Jonathan Wakely <[email protected]> ---
(In reply to Nate Graham from comment #10)
> There are basically two options:
> 1. Refresh when launching the app
> 2. Refresh when installing an app, uninstalling an app, or starting an
> update.


But there's another option:

Don't refresh if the cache was already refreshed in the background "recently"
(for some value of recent).

We know if refreshes in the background, because the systray widget appears when
it refreshes and new updates have been detected. So the system refreshes the
cache in the background, makes the "Updates available" widget appear in the
systray, I click on it immediately ... and then have to wait while it
re-refreshes the cache which is only a few seconds old.

Why is it necessary to refresh again when you open Discover, or start the
updates?

DNF doesn't do that. If I run it twice, the second time won't refresh the
cache:

~$ sudo dnf check-update
Updating and loading repositories:
 RPM Fusion for Fedora 42 - Nonfree - Updates                                  
                                    100% |   5.2 KiB/s |   7.9 KiB |  00m02s
 RPM Fusion for Fedora 42 - Free - Updates                                     
                                    100% |   6.5 KiB/s |   7.7 KiB |  00m01s
 Fedora 42 - x86_64 - Updates                                                  
                                    100% |  16.8 KiB/s |  18.7 KiB |  00m01s
Repositories loaded.
~$ 
~$ 
~$ sudo dnf check-update
Updating and loading repositories:
Repositories loaded.
~$

If new packages appeared in the repos between the first and second
`check-update` command, I wouldn't know about them. I would have to add the
`--refresh` option to force DNF to re-fetch.

If Discover did the same thing (only refreshing when the cache is stale, or the
user clicks Refresh) it would mean that some updates are potentially "missed"
if they were published after the last refresh. The user wouldn't get those
updates until the next time the cache is refreshed (automatically in the
background, or by pressing the Refresh button). But that is apparently
acceptable for DNF. Surely that's a possibility for Discover too?

"We don't want to do that" is a valid response, but "there are only two options
and this isn't one of them" just seems untrue.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to