Warning, /pim/akonadi/metainfo.yaml is written in an unsupported language. File is not indexed.

0001 name: akonadi
0002 description: PIM Storage Framework
0003 maintainer: dvratil
0004 group: kdepim
0005 type: solution
0006 platforms:
0007     - name: Linux
0008 public_lib: true
0009 libraries:
0010     - cmake: KPim6::AkonadiCore
0011     - cmake: KPim6::AkonadiWidgets
0012 cmakename: KPim6AkonadiCore
0013 # TODO: kapidox currently assumes: one product == one metainfo.yaml == one cmake config file
0014 # listing KPim6AkonadiAgentBase, KPim6AkonadiAgentBase, KPim6AkonadiWidgets, KPim6AkonadiXml as separate
0015 # packages in CMake's worldview needs changing kapidox first -> https://bugs.kde.org/show_bug.cgi?id=410452
0016 irc: akonadi
0017 
0018 group_info:
0019     fancyname: KDE PIM
0020     maintainer:
0021         - mlaurent
0022         - dvratil
0023     irc: kontact
0024     mailinglist: kde-pim
0025     platforms:
0026         - Linux
0027     description: KDE PIM provides set of libraries and application to access and
0028                  manage personal information like emails, contacts, events, etc.
0029     logo: docs/kontact.svg
0030     long_description:
0031         - KDE PIM provides a set of libraries and applications to access and
0032           manage personal information like emails, contacts, events, etc.
0033         - KDE PIM provides a set of libraries to parse and interact with various
0034           standardized PIM data formats, like RFC822 (KMime), ICAL (KCalendarCore)
0035           or VCARD (KContacts).
0036         - The backbone of the entire suite is Akonadi, the PIM storage framework.
0037           Akonadi provides unified API to access and manage any kind of PIM data
0038           regardless of the actual storage backend.
0039         - There are quite a few other libraries that provide PIM-specific widgets
0040           and utilities and can be useful for application developers who need to
0041           work with PIM data in their projects.
0042         - Please note that unless stated otherwise, none of the libraries have
0043           stable API or ABI as of now. We are trying to keep the changes small and
0044           we always announce big changes ahead on the mailing lists, but as the
0045           project evolves we might need to adjust some API here and there.