To make it clear, instead of spending time finding a way to disable akonadi/nepomuk, what is more and more requested is the possibility to not install/activate akonadi/nepomuk for users who do not use akonadi/nepomuk and programs requesting akonadi/nepomuk.

"The user better knows what he wants to do than OS"

It is now crazy that even rekonq is depending on ... libnepomuk.so.4, but hopefully does not request nepomuk to be activated.
Some cleaning is expected in the dependencies.

These dependencies are imposed by the system many KDE applications use to load faster. In this case, kdeinit4 links to the most commonly used libraries, then when the application wants to launch it simply forks itself and the fork then loads up the application.

bcooksley wrote:These dependencies are imposed by the system many KDE applications use to load faster.

??
Where did you read that nepomuk is speeding up the system ?
It looks like a joke, especially for a web-browser which has nothing to do with nepomuk.

If you read this:
"To make it clear, instead of spending time finding a way to disable akonadi/nepomuk, what is more and more requested is the possibility to not install/activate akonadi/nepomuk for users who do not use akonadi/nepomuk and programs requesting akonadi/nepomuk.",
I suppose you understand the target of this is not to slow down the system and to increase your CPU and hard-disk activities.

Nepomuk itself doesn't speed the system up. However, Nepomuk is registered with kdeinit4, the system many KDE applications use to start faster. As a result, those applications have an apparent dependency on libnepomuk even though they aren't.

It is a year later and still, the only replies by Mods/Admins to repeated user requests for ability to remove Akonadi/Nepomuk/Strigi remains... "you can disable them". My question is: "If we can disable them, why can't we remove them? And better yet... Why can't we choose to install KDE without Strigi (Akonadi/Nepomuk)? If we can, please tell me how, because after hours of search, my only findings are multitudes of requests for their removal.

Case in point. I looked into compiling KDE without Akonadi/Nepomuk/Strigi. Compiling kdebase-runtime has 3 dependencies and strigi is one of them. Yet in 'system settings' I can turn off strigi?!? Kind of makes you wonder if "turning it off" really "turns it off".

I would suggest limiting usage of capital letters....

The reason why it cannot be "removed" is because the developers should not have to support two different types of build - one for Nepomuk being enabled and one for being disabled. Disabling it selectively would complicate things hugely, and would increase the maintenance effort for the code in question.

bcooksley wrote:I would suggest limiting usage of capital letters....

Taken care of

bcooksley wrote:The reason why it cannot be "removed" is because the developers should not have to support two different types of build...

Thank you for the response. I would just like to confirm, before deciding on moving on to a diff DE... I ask, because I'm not too familiar with the process (but I will find out, depending on the response)... To build KDE, I need attica-*, soprano-* and strigi-*. Is there any kind of a workaround to compiling KDE without soprano/strigi (removal/alternatives, etc...) If I can build kdebase-runtime without/around them, I'd be set. Again... Thank you.

kdebase-runtime (much like kdelibs) can be built without Soprano and Strigi I believe. Not sure about Attica however. You will not be able to build the Workspace or PIM applications without Soprano/Strigi however.

+1 for optional compiling of this semantic piece of c*ap!

+1
I just want a light KDE base desktop without any nepomuk akonadi strigi stuff. Only the desktop, systemsettings, konsole and dolphin.

+1

semantic desktop is hell. Get rid of it. We want KDE light.