| Summary: | Allow Discover to skip checking for updates on filtered Flatpak packages | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | yizel7 |
| Component: | Flatpak Backend | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | aleixpol, jgrulich, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
yizel7
2021-11-02 17:12:00 UTC
Hmm, unsure. This seems pretty like a pretty niche thing specific to people who want to install updates the moment they become available. You can just not do that and let them pile up a bit, installing them on a schedule of your choice. (In reply to Nate Graham from comment #1) > Hmm, unsure. This seems pretty like a pretty niche thing specific to people > who want to install updates the moment they become available. You can just > not do that and let them pile up a bit, installing them on a schedule of > your choice. It's more about the Discover Update notification showing all the time. I currently have it set to "show when relevant". Due to these emulators it is showing all the time. This made me change the Discover Notification update to "hidden" because I didn't want to see it all the time. But now say Firefox has an update, I wouldn't know unless I go out of my way to check if there are updates. This is why it would be nice to be able to filter certain flatpaks from notifying unless I explicitly check myself. In this case, giving the user a choice. If you still disagree with the above reasoning, I am willing to concede and this ticket can be closed. Let's let Aleix decide. :) I understand it can be annoying, I'm not sure what's a good way to decide that an app is being annoying though. In fact, maybe a good way forward here would be to go tell the developers to only release new versions when they have something to show. We can check when the applications deploy dir changed last, which I understand it would tell us when we last changed (flatpak_installed_ref_get_deploy_dir), but still how do we know it's a pointless update? It could well be that 2h after releasing, firefox did a patch update because they found a security bug and you surely would want the updates there. I'd suggest to either: - contact the packagers. - install the stable branch of the apps that annoy you. - enable unattended updates. We could improve a bit the behaviour on unattended updates, if you decide to go that route we can sure have a discussion, as you might still be getting some notifications. I agree. :) (In reply to Aleix Pol from comment #4) > - enable unattended updates. We could improve a bit the behaviour on > unattended updates, if you decide to go that route we can sure have a > discussion, as you might still be getting some notifications. I was not aware unattended updates was a thing for Flatpaks. Is this a Discover setting? I don't see an option for it with flatpak --help |