On Mon, 9 Jan 2012 11:37, Roger Luedecke
wrote: On Mon, 2012-01-09 at 04:50 +0100, Yamaban wrote: <snip>
PS: Sorry for the rant, but the polkit hassle is just to much to bear. The memory used by polkit and consorts can be used better elsewhere.
I forked this discussion since I didn't want the thread hijacked. I think your scheme is very reasonable. However, frankly policykit has rarely gotten in my way or caused trouble... only in KDE, and mostly with Apper.
Honestly, KPackageKit/Apper has been a thorn in our side long enough. I really haven't much hope of getting it settled. Plus, it is simply overkill for simply doing updates. And as a package management tool, it is inadequate for the way we do things. What I mean by the last statement is since we often have different versions of a piece of software in different repos, and many of us have those repos, Apper fails to show why there are duplicate packages and doesn't give the versions. This is sloppy at best, potentially dangerous at worst.
Sorry, thread-jacking wasn't my intention. More laying the blame where it belongs, and a proposal of a workaround. Understood, but it was a very different topic then a QA team.
On Apper's failings, I agree with you, but to be cautious: What info can apper get from the packagekit backend, all - incluing the different repos, repo-priorites, and depenencies? That is a good question.
If yes, then it's appers fault, and sloppy programming. If no, then packagekit should be held responsible. Considering these issues don't crop up with the Gnome updater and such, I should imagine it is Apper. Though the Gnome updater would seem to not understand when something is locked, and bumps me back to YaST to resolve the issue. This seems to be a packagekit issue more likely.
As I said sorry for all the work that's going down the drain, but: "No Work - No Cookie"
The already existing and identified troubles inside packagekit are many, and no real drive to solve them upstream could be found by me.
So before we bark at the moon:
- If we drop polkit, packagekit, and those packages that can not life without those, would OSS 12.2 be better OSS 12.1 than now? Why would we want to drop policykit?
- What are doing the other distros to update their packages? * RedHat / Fedora / Centos : Yum and ??? KDE version uses KpackageKit last I saw, which works fine for them. * Ubuntu / Debian : deb and ??? Ubuntu uses packagekit for updater, and synaptic/ Ubuntu Software Manager for general package management. * Mandrivia : ??? and ??? I think they use drakx for updates, but I'm not sure since I have had massive problems with running Mandriva. * Arch: ??? and ??? * openSUSE and SUSE : Yast and ???
- What the hell is used under Gnome on OSS 12.1 ? ( Sorry not on my 12.1 atm. )
- Let's get ugly but working, small, and fast: a TK/Tcl gui for zypper. Qt should be fine too. Heck, we could probably get away with a
On Mon, 2012-01-09 at 18:02 +0100, Yamaban wrote: privileged daemon that runs a check via zypper or w/e and then would pass its privileges to the YaST Online Updater.
- Yamaban, who says thanks for all the work you guys and gals do.
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org