For KDE profile include flatpak (otherwise discover is useless/broken)

[joewood9364]

describe the request

Discover is pre-installed but is doesn't do anything as it has no back-end. As soon as you -S flatpak the store actually starts working with flathub immediately so maybe just install flatpak automatically with KDE profile.

[Torxed]

Out of curiosity, does KDE have no backend for pacman natively? Does it have to be flatpak?

[ghost]

Out of curiosity, does KDE have no backend for pacman natively? Does it have to be flatpak?

discover can be used to update the system with packagekit, but it is heavily discouraged as it may introduce issues as per here.

for some reason plasma-meta pulls in discover, which can confuse new users on why they can't use it. i feel like the best solution would be to remove the plasma-meta package and pick out packages to explicitly install avoiding discover altogether.

[Torxed]

Out of curiosity, does KDE have no backend for pacman natively? Does it have to be flatpak?

discover can be used to update the system with packagekit, but it is heavily discouraged as it may introduce issues as per here.

for some reason plasma-meta pulls in discover, which can confuse new users on why they can't use it. i feel like the best solution would be to remove the plasma-meta package and pick out packages to explicitly install avoiding discover altogether.

I've created a cross-post on the upstream package plasma-meta !1 to see if we can drop discover from the meta package.

We would really want to avoid maintaining two package lists if possible, as it causes more strain on everyone.

But the suggestion is valid, so lets see what "upstream" says about the idea :)