Akonadi is useful to certain types of users, such as enterprise users, users with a significant amount of personal data, those who store personal information remotely, etc. Such users welcome the Akonadi framework. At the other end of the spectrum are users who have no data coordination needs yet still would like to use KDE PIM apps. One unpalatable option --- both for users and for KDE public relations --- is for such users not to use KDE PIM apps. Another option is to provide some kind of method to disable Akonadi. The traditional KDE approach is to let users decide how to configure their systems. KDE developers accomplished a significant milestone when they added options in Systems Settings to control the behavior of Nepomuk, including disabling. KDE developers could achieve another milestone with a similar approach toward Akonadi. Initially disabling Akonadi is straightforward: ~/.config/akonadi/akonadiserverrc StartServer=false. A remaining challenge is for all Akonadi enabled apps to honor the akonadiserverrc StartServer setting and function as stand-alone apps rather than function only within the Akonadi framework. Currently no run-time option exists to disable Akonadi within KDE PIM apps. Other than KAlarm, currently no options exist to compile other KDE PIM apps without Akonadi. Adding either support would be a great public relations effort for KDE developers as well as encourage many KDE users to again use KDE PIM apps. Reproducible: Always
kdepim* uses akonadi so we can't do it. Close
(In reply to comment #0) > > Initially disabling Akonadi is straightforward: > ~/.config/akonadi/akonadiserverrc StartServer=false. > Note: This statement is completely wrong. StartServer doesn't disable Akonadi. It tells Akonadi to use an external database.
> kdepim* uses akonadi so we can't do it. So this is non-negotiable? End of discussion?
end of discussion yes. Kdepim uses it that's all.