When I try to uninstall the snap backend from discover, it tells me that it would uninstall discover as well. Wtf?
I hate snap more and more. It gets flooded with commercial stuff these days, and I don’t want it. I have one program installed from snap that isn’t available in flatpak (timeline), but I consider removing it as well, just because of how much I hate snap.
Which program did you use when trying to remove the package?
I’ve tried apt, apt-get and aptitude and the first two would only remove plasma-discover-backend-snap while the latter would also remove libsnapd-qt6-2-1
Neither would remove discover’s main package or any of the other backends.
Ok. When trying to do that from within discover, it told me that discover would also be uninstalled. Weird.
Debian packages can have different types/levels of dependencies.
Different tools can use different policies when resolving the dependency tree and thus make different decisions.
Two of the three tools I tried would have left the library package installed while it is no longer needed (they both said it could be removed and suggested a command to do that).
The dependency resolve in Discover might just be more “thorough” since it is a “store-like” frontend rather than a traditional package manager.
Agreed, or it is a bug in Discover, or packagekit’s apt backend.
$ sudo apt remove snapd plasma-discover-backend-snap
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following package was automatically installed and is no longer required:
libsnapd-qt6-2-1
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
plasma-discover-backend-snap snapd
0 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
After this operation, 127 MB disk space will be freed.
Do you want to continue? [Y/n]
