Making Akonadi configuration stateless and declarative

Brainstorm
1

I do not know the internals of Akonadi, but AFAIK Akonadi’s configuration is stateful:

  • If you look into ~/.config/akonadi, agent instances are enumerated, with the assigned number depending on the order in which the agents were set up.
  • By looking into akonadiconsole, the same seems to hold for collection IDs.

This makes it hard to configure Akonadi agents declaratively, i.e. by copying certain configuration files from one machine to the other. This is why I would like to make Akonadi’s configuration stateless.

3 Likes
2

Relevant issue:

I tried to look into Jonathan Marten’s comment regarding akonadiclient and requiring extensive rewrite in the PIM ecosystem but I couldn’t make sense of how akonadi agents handle configuration

1 Like