On 8/19/2012 5:41 AM, Rajko wrote:
On Sun, 19 Aug 2012 05:30:45 +0200 "Carlos E. R." <carlos.e.r@opensuse.org> wrote:
before the “locals” answer to remove apper and PK.
At least you and Carl are "locals" here and there, so if you can take action that will rather allow debugging, like explain how to disable Apper when it misbehaves, so it is not in the user way, but it can be enabled, updated and checked again.
What this can accomplish? Allow to fix bugs and, possibly, add some missing bits.
(I have disabled Apper, not removed, tossed in a hole, buried and stomped few times on top of it to make sure it will not appear again :)
They said they are fine with just removing pk/apper. They are saying whoever wants apper/pk used and fixed instead of hated and discarded, then they who have that interest should probably do that. Myself I'm fine with either. I don't care about it enough to fix it or advocate fixing it. I discard it every time, especially since my systems aren't desktops. Yet if it worked well and didn't cause problems I would not exactly resent the existence of the useful feature. It sounds like it's very close to being a good system with just a little locking and signal handling bug. It sounds like a lot of good work in danger of going to waste. If _I_ had done all the work necessary to develop such a system system to that level of functionality, _I_ would certainly want to clear up that little remaining bug rather than see all my work wasted and see the OS lack the useful feature. But I didn't write that stuff, and, I don't even use it, so I have no interest in convincing anyone to use it or fix it. My only interest is, I would prefer the OS to have as few bugs as possible, whether they are in systems I use or not, since they reflect on the OS entirely, which affects it's popularity, which affect the level of quality and support I get, both from suse and from the community and google. So I don't care whether apper/pk gets fixed, or gets discarded, I just care that it doesn't stay in while being buggy. I say discard it. For this reason: The problem has existed and been known already for a long time, so if the relevant developers & maintainers haven't already taken the steps Raijko & Carlos described some time ago, or if they have taken thise steps and still been unable to fix it, then to me that indicates they lack either the interest or the ability to support the package properly, which means discarding it is better than fixing it, because any fix will only be just todays fix and the underlying developer support problem will still be there causing problems indefinitely in the future. If the package gains other maintainers then that could be revisited in that eventuality. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org