Akonadi and MySQL

[Matthew Rosewarne]

There's no way around it: Akonadi needs MySQLd.

The goal is to somehow allow Akonadi to do what it needs to do without 
requiring the user to mess around with MySQL configuration.  The Akonadi 
service can either start & manage its own mysqld (one instance per user), or 
it can share one mysqld (one instance per system).

Currently mysqld is part of the mysql-server-* packages, which always installs 
init scripts for mysql, requires the user to set a root password, etc.

So the options would seem to be:
	1. Split out mysqld and minimal support files (without init scripts and such) 
		and let Akonadi start it.
	2. Perhaps use dbconfig-common to handle database instances, somehow do the 
		initial setup (root password and such), and make Akonadi use that instance
		instead of starting its own.
	3. Something else?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20080818/7fad6f12/attachment.pgp