Commit f3fc51af authored by Pino Toscano's avatar Pino Toscano

drop unused/useless files

parent a0974eac
akonadi (1.3.1-3+squeeze1) stable-proposed-updates; urgency=low
The location of the socket used to communicate with the Akonadi server was
changed to better support home directories on network file systems. After
updating to this version, applications making use of Akonadi will only
work correctly after restarting both the Akonadi server and client
applications.
-- Modestas Vainius <modax@debian.org> Sat, 30 Apr 2011 12:50:31 +0300
1. Akonadi configuration
------------------------
Akonadi stores its settings and data in the subdirectory "akonadi" of the file
system locations specified by XDG Base Directory Specification [1a].
* Configuration files (e.g. akonadiserverrc) are stored in
$XDG_CONFIG_HOME/akonadi/ (defaults to ~/.config/akonadi/). If the file
cannot be found there, Akonadi will look in $XDG_CONFIG_DIRS/akonadi/
(defaults to /etc/xdg/akonadi/).
* Similary, data files are stored in $XDG_DATA_HOME/akonadi/
(~/.local/share/akonadi/ by default). If the needed resource cannot be found
there, Akonadi will look in $XDG_DATA_DIRS/akonadi/ (that is
/usr/local/share/akonadi/ and /usr/share/akonadi/ by default) as well.
Please note that Akonadi never modifies config and/or data files in global
directories. Changed files are always written to $XDG_CONFIG_HOME/akonadi/ and
$XDG_DATA_HOME/akonadi/ respectively which will always have preference over
global files the next time Akonadi starts up.
[1a] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
2. Akonadi storage backends
---------------------------
While Akonadi provides data caching, indexing and searching services for PIM
applications, it does not do most of raw data manipulation itself. It relays
these tasks to the external SQL database engine. Flexible Akonadi architecture
allows a user to choose from a range of well-known SQL database servers and use
them with Akonadi.
SQL server specific details are implemented in Akonadi storage backends which
are provided by the respective akonadi-backend-* packages. Just install the
backend package which is the most appropriate for your setup and edit
akonadiserverrc configuration file accordingly. By default Akonadi uses MySQL
backend which is configured to start a local instance of MySQL server for each
user using Akonadi.
At the moment, the following backends are supported:
* MySQL backend (default) provided by the akonadi-backend-mysql package.
By default, the backend starts MySQL Server instance with privilegies of the
user that started akonadiserver. Alternatively (with StartServer=false) the
backend may connect to the specified database on the external MySQL server.
This backend uses official QSql MySQL driver. The following configuration
options are available:
[%General]
Driver=QMYSQL
[QMYSQL]
StartServer= ; whether to start internal server instance, defaults to true
Name= ; database name
Host= ; name of host running external MySQL server
User= ; database user, external server only
Password= ; database user password, external server only
Options= ; connection options
ServerPath= ; absolute path to the mysqld executable,
; defaults to /usr/sbin/mysqld, internal server only
CleanServerShutdownCommand= ; a command to shutdown internal server cleanly
; default is reasonable
* PostgreSQL backend provided by the akonadi-backend-postgresql package. Like
MySQL backend, by default PostgreSQL backend starts an unpriviledged instance
of the PostgreSQL server for each user. Alternatively, if you switch
StartServer option off, you may specify an external PostgreSQL database to
connect to.
This backend uses QSql PSQL driver. The following configuration options are
available:
[%General]
Driver=QPSQL
[QPSQL]
StartServer= ; whether to start internal server instance, defaults to true
Name= ; dababase name
Host= ; name of host running external PostgreSQL server
User= ; database user, external server only
Password= ; database user password, external server only
Options= ; connection options
ServerPath= ; path to the pg_ctl executable, internal server only
InitDbPath= ; path to the initdb executable, internal server only
CleanServerShutdownCommand= ; a command to shutdown internal server cleanly,
; default is reasonable
* SQLite backend provided by the akonadi-backend-sqlite package. It uses
embedded SQLite database hence it does not need a separate instance of the
SQL server.
This backend is based on the custom Qt SQLite3 driver which is
also shipped in the backend package. The following configuration options are
available:
[%General]
Driver=QSQLITE3
[QSQLITE3]
Name= ; path to the database file
; defaults to $XDG_DATA_HOME/akonadi/akonadi.db
NOTE: environment variables are not expanded in option values. Option must not
be present in the configuration file in order for its default to have effect.
* Wrong default ODBC configuration string for Debian virtuoso.
* debconf for switching default Akonadi backend?
* akonadi-backend package?
etc/akonadi/mysql-global-mobile.conf
etc/akonadi/mysql-global.conf
usr/lib/*/qt4/plugins/sqldrivers/libqsqlite3.so
usr/bin/akonadi_agent_launcher
usr/bin/akonadi_agent_server
usr/bin/akonadi_control
usr/bin/akonadi_rds
usr/bin/akonadictl
usr/bin/akonadiserver
usr/share/dbus-1/services/org.freedesktop.Akonadi.Control.service
usr/share/mime/packages/akonadi-mime.xml
...@@ -2,6 +2,11 @@ akonadi4 (1.13.0-12) UNRELEASED; urgency=medium ...@@ -2,6 +2,11 @@ akonadi4 (1.13.0-12) UNRELEASED; urgency=medium
[ Pino Toscano ] [ Pino Toscano ]
* Switch Vcs-* fields to salsa.debian.org. * Switch Vcs-* fields to salsa.debian.org.
* Remove not useful packaging files:
- install/man/etc files for binaries not built anymore
- TODO file: this source will not get further development
- NEWS & README.Debian: specific for the daemon, not for the library
- unused *.acc files
-- Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Fri, 13 Jul 2018 07:11:28 +0200 -- Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Fri, 13 Jul 2018 07:11:28 +0200
......
<?xml version="1.0" encoding="utf-8"?>
<descriptor>
<version>
1.12.0
</version>
<headers>
/usr/include/akonadi/abstractsearchplugin.h
/usr/include/akonadi/private
</headers>
<libs>
/usr/lib/libakonadiprotocolinternals.so
</libs>
</descriptor>
.TH AKONADI "1" "July 2015" "Akonadi 1.13.0" "User Commands"
.SH NAME
akonadictl \- Akonadi server manipulation tool
.SH SYNOPSIS
.B akonadictl
[\fI\,command\/\fR]
.SH DESCRIPTION
.SS "Commands:"
.TP
start
: Starts the Akonadi server with all its processes
.TP
stop
: Stops the Akonadi server and all its processes cleanly
.TP
restart
: Restart Akonadi server with all its processes
.TP
status
: Shows a status overview of the Akonadi server
.TP
vacuum
: Vacuum internal storage (WARNING: needs a lot of time and disk space!)
.TP
fsck
: Check (and attempt to fix) consistency of the internal storage (can take some time)
.SH OPTIONS
.SS "General options:"
.TP
\fB\-h\fR [ \fB\-\-help\fR ]
show this help message
.TP
\fB\-\-version\fR
show version information
.SS "Multi-instance options:"
.TP
\fB\-\-instance\fR arg
Namespace for starting multiple Akonadi instances in
the same user session
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment