Automatically refresh Update Manager when package cache or installed packages change #441
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gm10
changed the title
clefebvre
changed the title
Related changes: - refactor AutomaticRefreshThread(), and - have the application window insensitive until the application is fully loaded and the initial refresh finished
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Meant to add this for ages.
This only monitors changes to the package cache and dpkg's status, not to apt's configuration, so changing pins, repositories or similar without also refreshing the cache won't be caught. Intentional trade-off, the added complexity and resource usage are not worth monitoring that as well.
This also refactors the AutomaticRefreshThread and no longer cancels the scheduled refresh on exception.
Finally I did a pass over some of the log messages.