KDE PIM/Akonadi/Firstrun: Difference between revisions
(Start to document Akonadi Firstrun) |
|||
| Line 11: | Line 11: | ||
== How does it work? == | == How does it work? == | ||
The agents Akonadi Firstrun sets up as well as their configuration are defined by description files. These are searched for in ''$KDEDIR/share/apps/akonadi/firstrun'' and ''$KDEHOME/share/apps/akonadi/firstrun'' (exact paths may vary depending on your distribution). | |||
When starting a Akonadi application, Firstrun checks if there is a description file that has not been executed yet and, if so, does that. This means that starting the first Akonadi application will create the intial agents as well as that you can add additional description files later on to augment existing setups. | |||
== How do I create a Akonadi Firstrun description file? == | == How do I create a Akonadi Firstrun description file? == | ||
Revision as of 19:22, 29 April 2010
Akonadi Firstrun
This page documents the Akonadi Firstrun framework and how to use it to customize initial Akonadi setups.
What is Akonadi Firstrun?
Akonadi Firstrun allows you to automatically set up Akonadi agents. The most common use case is to provide an initial setup for new users.
Akonadi Firstrun is easily customizable, allowing distributions and system administrators to provide an optimized setup for their users.
How does it work?
The agents Akonadi Firstrun sets up as well as their configuration are defined by description files. These are searched for in $KDEDIR/share/apps/akonadi/firstrun and $KDEHOME/share/apps/akonadi/firstrun (exact paths may vary depending on your distribution).
When starting a Akonadi application, Firstrun checks if there is a description file that has not been executed yet and, if so, does that. This means that starting the first Akonadi application will create the intial agents as well as that you can add additional description files later on to augment existing setups.
How do I create a Akonadi Firstrun description file?
TODO