Arch Linux

CrazyAlex25

Member

From: Russia

Registered: 2024-03-21

Posts: 2

Website

KDE6 Akonadi default database backend

Why does akonadi's dependencies hardcode mariadb? Why not make sqlite the default (as it is already in qt6-base).

If we look at which packages depend on mariadb, we will see only 2 strictly dependent packages: akonadi and galera. Moreover, galera is a special application for mariadb. So it turns out that only akonadi strictly depends on mariadb.

I don’t want to install a full-fledged DBMS just for the sake of akonadi, because there is support for other backends!

I propose to make the dependency on mariadb optional.

https://gitlab.archlinux.org/archlinux/ … =heads#L64

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,196

Re: KDE6 Akonadi default database backend

Until very recently the Sqlite backend was strongly discouraged, but yeah since Qt6 it's actually reccommended now.

In order to reach the proper people with this feature request, you should open a relevant issue on the gitlab project.

FWIW - haven't investigated closer whether that's really the case - chances are if you build in support it can't be made optional from a dependency/library loading perspective and thus the dependency has to be that way, even when switching the default backend for people not yet using Akonadi/PIM with the mariadb backend.

Mod note, not an Arch discussion, moving to Modifying Packages.

Last edited by V1del (2024-03-21 12:40:59)

CrazyAlex25

Member

From: Russia

Registered: 2024-03-21

Posts: 2

Website

Re: KDE6 Akonadi default database backend

At the moment, registration on gitlab is only upon request This was the first place I looked with the problem.

Regarding the optionality of backends: in debian\ubuntu there is a division into packages akonadi-backend-{mysql,postgresql,sqlite} which are optional for the akonadi-server package