On Sun, 8 Jan 2012 11:45, Roger Luedecke
wrote: I think in a previous thread we identified some issues, and some possible solutions.
I think to help assure the quality of our distro we need to create a QA team, with a good structure. One of the issues will be having strong centralized communication. I believe I can provide an excellent tool for this, as long as nobody is opposed to using an outside tool.
<snip>
Addenum to think of:
If one looks at what "polkit" does, and just HOW it violates FHS (modifications are done in /usr/..., /var/... is ignored/lower prio) it's no wonder that apps/services that build on this fuctionality (package-kit) fail to work properly.
Food for thought: - How do other distros handle the updates? - Which way is the most painless?
In earlier versions of openSUSE there was a wrapper called "you" for "yast2 online_update", this wrapper could be made 'priviledged' by simply addding a line to /etc/sudoers.
Then add a .desktop file for "you" and you have a working updater for everybody, even with gui!
To reintroduce this would stop the "need" for polkit. At least for updates. And this woud use YAST not any other "not-working-right-puppet".
Sorry for the work you put into the "update-applets", but without reliable backends (hello polkit!) they all fall short.
Should we (devs, packagers, users) make noise to remove polkit at all from 12.2 ? (Fix upstream fully or remove!)
Whitout the hassle of polkit the REAL trouble inside package-kit would be ripe for debugging.
- Yamaban.
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
On Mon, 2012-01-09 at 04:50 +0100, Yamaban wrote: 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. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org