What went wrong with the KDE 4 release?


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News What went wrong with the KDE 4 release?
# 1  
Old 07-15-2008
What went wrong with the KDE 4 release?

07-15-2008 11:00 AM
When KDE 4.0 was released in January, it was supposed to be the foundation for a new era of desktop development. But as 4.x versions began finding their way into distributions, negative reactions began to obscure other ones. With the upcoming 4.1 release due at the end of this month, it's hard to avoid wondering: what happened?



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
KDEINIT4(8)							 KDE User's Manual						       KDEINIT4(8)

NAME
kdeinit4 - Start all other KDE programs and kdeinit loadable modules (KLMs). SYNOPSIS
kdeinit4 [--help] [--no-fork | --no-kded | --suicide] [+programs | programs] DESCRIPTION
kdeinit4 is a process launcher somewhat similar to the famous init used for booting UNIX. It executes KDE programs and kdeinit loadable modules (KLMs) starting them more efficiently. Using kdeinit4 to launch KDE applications makes starting a typical KDE application a couple times faster and reduces memory consumption by a substantial amount. kdeinit4 is linked against all libraries a standard KDE application needs. With this technique, starting an application becomes much faster because now only the application itself needs to be linked whereas otherwise both the application as well as all the libaries it uses need to be linked. DISADVANTAGES
The process name of applications started via kdeinit4 is "kdeinit4". This problem can be corrected to a degree by changing the application name as shown by ps. However, applications like killall will only see kdeinit4 as the process name. To workaround this, use kdekillall (from kdesdk/scripts) for applications started via kdeinit4. OPTIONS
--help Show help about options --no-fork Do not fork, i.e. do not exit until all the executed programs ends --no-kded Do not start kded --suicide Terminate when no KDE applications are left running +programs runs the programs handling requests programs runs the programs without handling requests USAGE
A standard way to run this program is by simply specifying the following command at the prompt kdeinit4 program or kdeinit4 +program FILES
/tmp/kde-$USER/kdeinit4_$INSTANCE ... ENVIRONMENT VARIABLES
$HOME Specifies the home directory of the current user $KDE_HOME_READONLY Specifies if the home directory of the current user is read only $KDE_IS_PRELINKED If set, tells kdeinit4 that the KDE programs are pre-linked. (Prelinking is a process that allows you to speed up the process of dynamic linking.) $KDE_DISPLAY If set, tells kdeinit4 that it is running on a KDE desktop. SEE ALSO
kded, kdekillall BUGS
There are probably tons of bugs. Use bugs.kde.org: http://bugs.kde.org to report them. AUTHORS
Waldo Bastian <bastian@kde.org>, Mario Weilguni <mweilguni@sime.com>, Lubos Lunak <l.lunak@kde.org>. 2008-10-03 KDEINIT4(8)