[gnome-software: 1/2] gs-os-update-page: Mark installed apps for removal
- From: Milan Crha <mcrha src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-software: 1/2] gs-os-update-page: Mark installed apps for removal
- Date: Mon, 13 Dec 2021 13:04:53 +0000 (UTC)
commit b747cc81dca1bf063ea243c8eda9fb40928107cb
Author: Pablo Correa Gómez <ablocorrea hotmail com>
Date: Fri Dec 10 14:49:34 2021 +0100
gs-os-update-page: Mark installed apps for removal
When an app exists in the GsOSUpdatePage, it should have been
created by a plugin with the goal of adding, removing,
updating or downgrading it. Therefore, if the app is in the
GS_APP_STATE_INSTALLED, it should be safe for GS to assume that
the app has to be removed.
An example situation where this is useful is when an package
upgrade removes a dependency on an OS package and the "dependent"
package can then be safely removed. This might not be a big
matter in stable distros, but is definitely something that happens
often in rolling-release channels.
src/gs-os-update-page.c | 1 +
1 file changed, 1 insertion(+)
---
diff --git a/src/gs-os-update-page.c b/src/gs-os-update-page.c
index ed63163e5..d20f15e7d 100644
--- a/src/gs-os-update-page.c
+++ b/src/gs-os-update-page.c
@@ -201,6 +201,7 @@ get_app_section (GsApp *app)
section = GS_OS_UPDATE_PAGE_SECTION_ADDITIONS;
break;
case GS_APP_STATE_UNAVAILABLE:
+ case GS_APP_STATE_INSTALLED:
section = GS_OS_UPDATE_PAGE_SECTION_REMOVALS;
break;
case GS_APP_STATE_UPDATABLE:
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]