with Akonadi (QSQLITE3) by default. It behaves better for me, at least.
This won't affect existing installations. You can freely migrate from
QSQLITE to QSQLITE3 and back, just remember to stop Akonadi and make sure
that corresponding lines in ~/.config/akonadi/akonadiserverrc are pointing
to the same database file, then start Akonadi again.
a new libmysqlclient non-blocking API which utilizes co-routines. The X86
specific GCC ASM co-routine support hid the fact that there was an issue.
The only fallback code so far is POSIX user contexts which OpenBSD does not
support.
Input from and Ok sthen@ jasper@
Akonadi is a PIM layer, which provides an asynchronous API to access all kind
of PIM data (e.g. mails, contacts, events, todos etc.).
It consists of several processes (generally called the Akonadi server) and a
library (called client library) which encapsulates the communication
between the client and the server.
Note: Akonadi creates a cache of different data in ~/.local/share/akonadi,
using one or the other DB backend. By default, it uses (own) SQLite backend,
it behaves best here. If you change DB backend, you will NOT lose your data,
just the cache will need to be regenerated.
The old version in x11/kde4/akonadi will bite the dust soon.
ok landry@
