Hello, Until now I was happy with no kde-base/akonadi... I don't know why, as I see no change in overlay or portage tree, maybe the recent portage rc, I got the following: [nomerge ] kde-base/kdepim-kresources-4.2.2 USE="kdeprefix -debug" [0] [ebuild N ] kde-base/akonadi-4.2.2 USE="kdeprefix semantic-desktop -debug" 0 kB [0] [nomerge ] kde-base/kdepimlibs-4.2.2 USE="kdeprefix ldap sasl -debug -doc -test" [1] [ebuild R ] app-office/akonadi-server-1.1.1 USE="mysql*" 0 kB [0] Disable the mysql USE as it was until now causes: emerge: there are no ebuilds built with USE flags to satisfy ">=app-office/akonadi-server-1.1[mysql]". !!! One of the following packages is required to complete your request: - app-office/akonadi-server-1.1.1 (Change USE: +mysql) (dependency required by "kde-base/akonadi-4.2.2" [ebuild]) (dependency required by "kde-base/kdepim-kresources-4.2.2" [ebuild]) (dependency required by "kde-base/korganizer-4.2.2" [installed]) (dependency required by "@world" [argument]) Which is correct, as: kdepim-kresources-4.2.2 needs akonadi-4.2.2 akonadi-4.2.2 needs >=app-office/akonadi-server-1.1[mysql] With no conditions. So something is changed, if it is portage, now it behaves correctly... The question to kde team is this akonadi a true forced requirement or can be selected using a USE flag. If it is required, can users somehow can disable mysql installation? Thanks! Alon
+1 on this because akonadi's use of mysql broke my previously installed mysqld. It looks like it's possible to turn off akonadi's internal mysql server from: Computer, System Settings, Advanced, Akonadi configuration. Don't know yet if turning off internal server and not defining and external server will work (that test is next). I don't see how to say do use akonadi...
Turning off akonadi's internal server does appear to cause any problems with the caveat that I don't use KDE's PIM stuff. Actually turning off the internal server was all that was needed to get my original mysql working again.
I meant to say: Turning off akonadi's internal server does NOT appear to cause any problems... Sorry.
Anyone? Not anyone wish to index files... And mysql installation is a large requirement. So maybe drop the akonadi-server force dependency? or akonadi?
There is useflag mysql for this reason dropping akonadi, so please just read what meta packages do. It can be already dropped for cost of not having some pim packages.
Well, The kdepim-kresources was modify to not require mysql for akonadi, so this problem was fixed.
