FS#29208 - [kdepimlibs] mark akonadi as optional dependency

Attached to Project: Arch Linux
Opened by Martin Sandsmark (sandsmark) - Saturday, 31 March 2012, 21:05 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 April 2012, 11:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Inspired by a similar change tested in opensuse, it would be neat if kdepimlibs didn't necessarily pull in akonadi, as it isn't a strict runtime requirement for kdepimlibs itself.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 04 April 2012, 11:17 GMT
Reason for closing:  Won't implement
Additional comments about closing:  No need
Comment by Andrea Scarpino (BaSh) - Sunday, 01 April 2012, 08:29 GMT
AFAIK akonadi is even needed by the Clock plasmoid now.

If we split kdepimlibs, we should disable akonadi playing with the config files, and you know: we ever keep the upstream configuration.
Comment by Martin Sandsmark (sandsmark) - Sunday, 01 April 2012, 12:17 GMT
But the clock plasmoid isn't in kdepimlibs? And AFAIK it should still run fine without akonadi, it should be an optional runtime dependency.
Comment by Andrea Scarpino (BaSh) - Sunday, 01 April 2012, 12:20 GMT
No, the clock plasmoid is in kdebase-workspace.
Comment by Andrea Scarpino (BaSh) - Wednesday, 04 April 2012, 11:16 GMT
From http://userbase.kde.org/Akonadi
"If you don't want to have Akonadi running on your system, you can not use any of the Akonadi-enabled applications. Such applications will start Akonadi, whenever they need its services even if you have disabled it. See the list of Akonadi-enabled applications. Also note, that some Plasma widgets, such as the Digital Clock uses Akonadi"

Loading...