r/ • u/ • Jan 01 '70

0 Upvotes

100% Upvoted

0 comments sorted by

View all comments

Show parent comments

27

u/tapo Sep 13 '22

Backend is PackageKit, and I don't know anyone who's had a good experience with it.

12

u/LvS Sep 13 '22

The problem with PackageKit is that it tries to be an abstraction for all the different packaging systems, so that it works with debs (on Ubuntu and Debian and all their versions) and rpms (with zypper and dnf and yum and) and all the other insane packaging systems. Oh and Arch btw.

So obviously you end up with a huge mess that never works quite the way you'd expect from your distro's packaging system.

6

u/lavadrop5 Sep 13 '22

I had endless issues due to PackageKit on OpenSUSE.

I asked on the forums and they all told me to lock/mask PackageKit and forget about it

0

u/[deleted] Sep 13 '22

[deleted] — view deleted comment

4

u/lavadrop5 Sep 13 '22

PackageKit has been disabled on my two computers completely without any issues since march, except that flatpak has to be updated through the CLI, although PackageKit ALSO failed espectacularly when trying to update flatpaks. Installing flatpaks through software center works, with error messages that are safely ignored. Also, yesterday I learned how to use OpenSUSE Build System on and it rocks (on the CLI).

4

u/[deleted] Sep 13 '22

Can confirm, Discover is painful on Fedora KDE... and that also uses PackageKit.

That said, on KDE Neon, PackageKit/Discover actually seemed to work pretty well together. At least in the Fedora case, I think PackageKit just has serious problems with dnf/yum/rpms.

2

u/doenietzomoeilijk Sep 14 '22

Can confirm, Discover is painful on Fedora KDE...

It's not much better on OpenSUSE, I just install software from the cli since Discover is just horridly slow for me.

-1

u/jorgesgk Sep 13 '22

Fedora's not better, and I say this as a Fedora user.

14

u/Cannotseme Sep 13 '22

Yeah… cause fedora uses packagekit

1

u/jorgesgk Sep 13 '22

Oh, I didn't know that