[SOLVED]KDE Plasma 5.27 and flatpak + flatpak-kcm

Pyntux · 2023-02-16 23:21:48

So, after updating to Plasma 5.27, there was update with flatpak + flatpak-kcm.... I really do not need to have flatpak on my system... So I removed those 2, but "plasma-meta" first, because of dependency cycle... After that, pacman -Qdt says:

[punky@T460 ~]$ sudo pacman -Qdt
bubblewrap 0.7.0-1
kde-gtk-config 5.27.0-1
kdeplasma-addons 5.27.0-1
kgamma5 5.27.0-1
khotkeys 5.27.0-1
kwallet-pam 5.27.0-1
kwrited 5.27.0-1
libmalcontent 0.11.0-1
ostree 2022.7-1
oxygen 5.27.0-1
plasma-browser-integration 5.27.0-1
plasma-desktop 5.27.0-1
plasma-disks 5.27.0-1
plasma-firewall 5.27.0-1
plasma-systemmonitor 5.27.0-1
plasma-thunderbolt 5.27.0-1
plasma-vault 5.27.0-1
plasma-welcome 5.27.0-1
sddm-kcm 5.27.0-1
xdg-dbus-proxy 0.1.4-1
[punky@T460 ~]$

Is there way to remove flatpak but not to make those packages orphans (beside -Rdd) ?

Maybe to install all of that with "--asexplicit" flag?

Last edited by Pyntux (2023-02-17 06:03:58)

Versa · 2023-02-17 05:44:59

As you want to trim the number of packages to be less than what that group contains, the right way of handling this would have been to install plasma as a package group (plasma) and select the components you want rather than the meta package(plasma-meta) which doesnt allow trimming group members(they are all hard dependencies).

Since you already have the group members installed, for all the packages you want to keep in your packman -Qdt output, you can list them all at once in the following:

sudo pacman -D --asexplicit *package_names*

in order to update them all as explicitly installed while leaving out plasma-meta and the flatpak packages. Then you can trim the plasma group packages(including the meta and flatpak ones) as much as you want. Just make sure to not accidentally trim something you use though you can always reinstall that component later either with the copy in the packman cache(assuming its recent and you did not clear it out) or the regular method.

This does come with one notable downside. If the plasma group would get a new package added to it, you will not automatically be informed of it or install it. A good example is plasma-firewall package to enable GUI management of a firewall through plasma settings which is (relatively) new and I didn't see for months.

Last edited by Versa (2023-02-17 05:53:32)

Pyntux · 2023-02-17 06:03:37

Thank you!

All of this is problem because last time I installed Arch, I installed using "archinstall" script, which uses plasma-meta as installation method. When i install arch "manually" , I am using "plasma-desktop" package and than just add to that what I need.

Versa · 2023-02-17 06:35:53

Pyntux wrote:

When i install arch "manually" , I am using "plasma-desktop" package and than just add to that what I need.

Installing plasma as a group also presents all the group members and allows selecting what you want with ranges eg. [1-7] [9-22] 46, allowing you do add them all at once right there in a terminal:

sudo pacman -S plasma
[sudo] password for user: 
:: There are 47 members in group plasma:
:: Repository extra
   1) bluedevil  2) breeze  3) breeze-gtk  4) discover  5) drkonqi  6) kactivitymanagerd  7) kde-cli-tools  8) kde-gtk-config  9) kdecoration  10) kdeplasma-addons  11) kgamma5  12) khotkeys
   13) kinfocenter  14) kmenuedit  15) kpipewire  16) kscreen  17) kscreenlocker  18) ksshaskpass  19) ksystemstats  20) kwallet-pam  21) kwayland-integration  22) kwin  23) kwrited
   24) layer-shell-qt  25) libkscreen  26) libksysguard  27) milou  28) oxygen  29) oxygen-sounds  30) plasma-browser-integration  31) plasma-desktop  32) plasma-disks  33) plasma-firewall
   34) plasma-integration  35) plasma-nm  36) plasma-pa  37) plasma-sdk  38) plasma-systemmonitor  39) plasma-thunderbolt  40) plasma-vault  41) plasma-workspace  42) plasma-workspace-wallpapers
   43) polkit-kde-agent  44) powerdevil  45) sddm-kcm  46) systemsettings  47) xdg-desktop-portal-kde

Enter a selection (default=all):

You can also install the entire group explicitly and remove later, or as you mentioned install only plasma-desktop and add later.

Either way, any method other than using the meta package installs all the components explicitly and allows removal as you want at the cost of not automatically pulling new major additions that are not dependencies of plasma-desktop.

Last edited by Versa (2023-02-17 06:37:24)

Pyntux · 2023-02-17 18:26:09

Yes, but I follow the news and developments of Plasma, so it shouldn't be a problem... Thank you again!

EDIT:

I just removed "plasma-meta" with -Rn option, than flatpak support, and those "orphans" installed --asexplicit....

Last edited by Pyntux (2023-02-17 18:43:26)

Arch Linux

#1 2023-02-16 23:21:48

[SOLVED]KDE Plasma 5.27 and flatpak + flatpak-kcm

#2 2023-02-17 05:44:59

Re: [SOLVED]KDE Plasma 5.27 and flatpak + flatpak-kcm

#3 2023-02-17 06:03:37

Re: [SOLVED]KDE Plasma 5.27 and flatpak + flatpak-kcm

#4 2023-02-17 06:35:53

Re: [SOLVED]KDE Plasma 5.27 and flatpak + flatpak-kcm

#5 2023-02-17 18:26:09

Re: [SOLVED]KDE Plasma 5.27 and flatpak + flatpak-kcm

Board footer