In fact Akonadi apps and its whole system is totally broken, I tried many times to convince myself and use them but after certain time I'm totally blocked with many bugs that even caused me to loose important data and there is no work or any attempt to fix them even if they are already reported for many years, so it's unbelievable to think that someone is using Kontact or any of those broken PIM apps to manage contacts or mails, so the idea of linking this great app with some totally broken (that will never be fixed in years) packages is not logical at all.
Hi, The Akonadi dependency is really small in digiKam, and i share your viewpoint about Akonady. I was never convinced by this software component. Removing is easy to do. Maik, your viewpoint ? Gilles
I don't understand the problem, Akonadi is optional in digiKam and doesn't need to be compiled. I wouldn't remove it at the moment either. I've been using KMail myself for years and use the address book. Yes, I know the discussions but I read and write my emails with it every day. From time to time I also use the function in digiKam to create a person from the Akonadi address book as a tag. Maik
(In reply to Maik Qualmann from comment #2) > I don't understand the problem, Akonadi is optional in digiKam and doesn't > need to be compiled. On Arch based distros I see two dependency packages : akonadi-contacts and libakonadi that need to be installed to make Digikam usable. And as stated by Arch digikam maintainer those two package are needed to fulfill some kind of face detection based on kontact app which no one is using. https://bugs.archlinux.org/task/67631
Then this information from the package maintainer is wrong. Akonadi is not required for face detection and the Kontact app does not use face detection from digiKam either. Only the names from the address book are read and a tag can be created. It's really very simple in digiKam. Maik
(In reply to medin from comment #3) > by Arch digikam maintainer those two package are needed to fulfill some kind > of face detection based on kontact app which no one is using. No, the Arch digikam maintainer has never said such a thing > kontact app which no one is using. That's a pretty bold statement to make. Can you share the data that you've collected to back it up?
As I said, I very rarely use it in digiKam to create tags from the address book and since it is also not available on MacOS and Windows, the number of users using it is probably very small. I can live with it if we remove it. Just what's next? The Baloo support? We just fixed a lot in Baloo support last year and I was surprised that users want to sync their metadata with Dolphin and digiKam. @medin, what desktop are you using on Archlinux? Maik
(In reply to Antonio Rojas from comment #5) > No, the Arch digikam maintainer has never said such a thing It's not said, but clearly stated in dependency details that the installation of digikam requires (not optional) the installation of both akonadi-contacts and libakonadi (required by akonadi-contacts) packages or do I see it wrong ? https://archlinux.org/packages/extra/x86_64/digikam/ > kontact app which no one is using. Sorry but all PIM apps are garbage, I used them for long time and many already reported bugs that have high priority never got fixed. I wish Kalendar to be the exception of them.
> @medin, what desktop are you using on Archlinux? I'm using KDE.
Akonadi is optional at compile time and also disabled by default. Of course, if your distribution activates it, it is no longer optional and then requires the corresponding Akonadi libraries. We now have 2 options we play god and remove it or your distro won't enable it. However, there is then the possibility that other users will complain and we will then have the next bug report that the address book feature is no longer available. I only use KMail from the Kontact app, yes there were real downs a long time ago. But I use it every day and wouldn't use any other email program right now. Maik
I agree with Maik. Akonadi support is optional and disabled by default at compilation time. We can live with it for the moment. If you want to see the Akonadi support dropped in your native package, contact your favorite linux team to disable this option in build process. Gilles Caulier
(In reply to caulier.gilles from comment #10) > If you want to see the Akonadi support dropped in your native package, > contact your favorite linux team to disable this option in build process. The package maintainer for Arch is the same person who responded above Antonio Rojas.
Hi Medin, As i already said in comment #10, the Akonadi dependency is optional in digiKam and disabled by default. Just use right option with cmake to drop the dependency at compilation time. It's explained in the documentation here : https://www.digikam.org/api/index.html#cmakeoptions As it's disabled by default, this want mean that Arch Linux package definition turn ON explicitly this option. Turn OFF or remove the option will solve your problem... Best Gilles Caulier