9 Jan
2012
9 Jan
'12
22:53
On Mon, 9 Jan 2012 23:21, Roger Luedeckewrote: > On Mon, 2012-01-09 at 18:02 +0100, Yamaban wrote: >> On Mon, 9 Jan 2012 11:37, Roger Luedecke wrote: >>> On Mon, 2012-01-09 at 04:50 +0100, Yamaban wrote: >> >> 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. >> - 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? To quote a earlier message: "polkit violates the FHS" A easy test is to put /usr on a seperate partition and mount /usr readonly. Happy using polkit and applying your changes then. ATM polkit ignores any changes in /var if there's a corresponding rule in /usr. Recommendation: rewrite of the rule selection and change part. Without these changes: drop hard, and drop fast. You do not drive a car with a failing brakesystem, or do you? Polkit is a part of the security system, no failure allowed. >> - 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. - What does KpackageKit on Fedora different, than the one on OSS The backend, right? - How does Fedora it, calling yum or selfmade in KPK? >> * Ubuntu / Debian : deb and ??? > Ubuntu uses packagekit for updater, and synaptic/ Ubuntu Software > Manager for general package management. - See above: Backend to deb, or selfmade in packagekit? >> * Mandrivia : ??? and ??? > I think they use drakx for updates, but I'm not sure since I have had > massive problems with running Mandriva. - Thanks for the info. >> - 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 > privileged daemon that runs a check via zypper or w/e and then would > pass its privileges to the YaST Online Updater. The idea behind TK/Tcl was not dependeny on gnome/gtk and/or kde/qt. On the other hand, YaST does a good handling on gtk/qt/ncurses A not-an-applet, but a program which resides in the system-tray as an icon and works, no matter of qt / gtk / whatever would be the best, if not most harmonious solution. Ensurance of clean operation first, gimiks and style later. And please no updater should ever have any dependency on plasma, never! (let the sleeping dogs lay, no sense in tickling the sleeping dragons.) - Yamaban PS: what steps would one have to go to use the gnome-updater in KDE, and what are the failures of gnome-updater? (Removing the KDE part from the updater troubles) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org