Summary: | is kdeinit still necessary? | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | cb-kde |
Component: | kdeinit | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED LATER | ||
Severity: | wishlist | CC: | adjam7 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
cb-kde
2002-11-25 00:01:51 UTC
Once the new gcc/glibc/binutils are sufficiently mainstream we will reevaluate the need for kdeinit, apart from startup time it also improves page-sharing. We will need to look at some actual data to decide whether it is still worth to keep using kdeinit. Also note that KDE runs on a number of Linux-compatible platforms which do not all benefit from the improvements of gcc/glibc/binutils. I am very aware of the hackish aspects of kdeinit and its shortcomings. Don't worry ;-) Almost 3 years after the last comment, no news on this subject...? Nothing changed. Maybe in another 3 years. As of today, are there plans for KDE4 to still use kdeinit, or will it (finally) be ditched ? :-) kdeinit will be used in KDE4. With the recent additions to binutils such as: -DT_GNU_HASH -Bsymbolic-functions and this feature: http://dot.kde.org/1172617283/1172768274/1172773687/1172776025/ Will kdeinit with it's "hackish aspects" remain a reality in KDE4? DT_GNU_HASH doesn't work on FreeBSD as far as I know. Do you in comment #6 only care about Linux users? What about here? (More than) 3 years passed... |