Summary: | kdelibs4c2a is making trouble | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Hans-J. Ullrich <hans.ullrich> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 4.2.2 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Hans-J. Ullrich
2009-05-29 19:18:39 UTC
(In reply to comment #0) > Please let me explain: For example, there are 2 processes started (kded and > kded4) which do the same. The old one is started through kdelibs4c2a , the > other one through kdelibs5. This IMO is not necessary, isn't it? This is necessary, as KDE 3 and KDE 4 services are totally independent, and they general cannot interact anyway (different incompatible libraries, different inter-process communication system, etc). > The same is with the process kdeinit and kdeinit4, both do the same, but > loading both needs unnecessary cpu power. kdeinit and kdeinit4 stay idle if there's no work for them. > The third thing, I discovered, is that a lot of processes (20 and more) named > kio-httpd are started (each uses 4M of RAM), which seem caused of the described > problem above. Unrelated. > So, as there are still lots of applications (amarok is one of them, kpowersave, > and lots more) which still need kdelibs4c2a, it is a big problem, to change > them all. Otherwise, users should not be forced to remove them, just because > they want to use KDE-4! I don't agree this is an big problem, or even some problem. > So, my idea is, to merge kdelibs5 and kdelibs4c2a, so you get ONE library for > all, or , the other option might be, to eliminate all functions out of > kdelibs4c2a, which are already done by kdelibs5. This cannot be done, as (as said above) KDE 3 libraries and KDE 4 ones are totally independent. You cannot make KDE 3 applications use KDE 4 libraries, and vice versa, this is impossible to do. The bottom line is: we designed to make KDE 3 applications runnable in a KDE 4 desktop and vice versa, so services for both _are_ needed. More and more applications are getting ported to KDE 4, so over time you'll have gradually less running KDE 3 applications. |