Groups | Search | Server Info | Login | Register

Groups > linux.gentoo.dev > #70538

[gentoo-dev] Re: [RFC] News Item: KDE PIM 26.04.1 default backend changes to sqlite

Show all headers | View raw

Most of the following suggested changes are niggles, but IMO niggles that
as-is mark the author as a likely English as a second language speaker/writer.
The suggested changes read more naturally to me.

Arguably more important are the table-move, systemwide vs. per-user actions
emphasis, and omission of "preferred" in the dispatch-conf/etc-update reminder.

Of course all suggested changes are my opinion and the call whether to actually
make them or not is yours.  =:^)

Andreas Sturmlechner posted on Tue, 12 May 2026 00:15:46 +0200 as
excerpted:

> KDE PIM's centralised Akonadi subsystem is using a database for cached data.

s/is using/uses/

> For this, three different database backends are supported for a long time.

s/are/have been/

> When multiple USE flags are enabled, kde-apps/akonadi-config ebuild picks

s/, kde-apps/the kde-apps/

> the one with highest priority as default DB backend in akonadiserverrc.

s/highest/the highest/
s/default/the default/

> ---------!--------------------------------!-----------!-----------
>  Backend ! kde-apps/akonadi-config[<use>] ! <=26.04.0 ! >=26.04.1
> ---------!--------------------------------!-----------!-----------
>  QSQLITE ! sqlite                         !     2     !     1
>  QMYSQL  ! mysql                          !     1     !     2
>  QPSQL   ! postgres                       !     3     !     3
>                                           !  (priority, 1 = best)

Move the priority line to the top of the table from the bottom?

Also, the table as a summary is an /excellent/ idea, but (IMO) what
it does is summarize the changes, so it should go under changes.

Of course that moves it from immediately under the "highest priority"
mention currently just above the table, leaving that without immediate
context.  Thus I'd put a lookahead there, as in (with the changes
suggested above):

When multiple USE flags are enabled the kde-apps/akonadi-config ebuild picks
the one with the highest priority (see the table under Changes below)
as the default DB backend in akonadiserverrc.

> This means that prior to KDE PIM 26.04.1 (with kde-apps/akonadi-config-0),
> mysql, when enabled, took precedence for new KDE PIM setups.
> 
> 
> Changes
> =======
> 
> With kde-apps/akonadi-config-1 we are making sqlite first choice instead.

s/first choice/the highest priority/

> That in itself will not change existing Akonadi instance settings, which
> are stored in home directories.

s/, which/as they/

[The table would move here]

> Reasons
> =======
> 
> Historically[1], QSQLITE backend was fundamentally broken for KMail workload,

s/QSQLITE/the QSQLITE/
s/KMail/KMail's/

> User Action Required
> ====================

The suggested changes are in the user HOME dir and thus need to be made
per-KMail-using user.  I'd suggest making that more explicit as below:

> In order to implement any backend change on your users' akonadi DB config,
> a manual migration step is necessary - in this example, from mysql to sqlite.
> It is necessary to have support for both database drivers enabled in
> dev-qt/qtbase for this to succeed.

s/It is/First, systemwide, it is/

>     1) Find out which backend is currently in use:
> 
>         grep ^Driver ~/.config/akonadi/akonadiserverrc
> 
>     2) A quick check that both DB drivers are supported by Qt:
> 
>         USE="mysql sqlite" emerge -p1 dev-qt/qtbase
> 
>         If this command indicates a USE flag change, you must at least
>         temporarily rebuild dev-qt/qtbase with both old and new enabled.
+
+Then for each KMail-using-user:

>     3) Migration:
> 
>         akonadi-db-migrator --newengine sqlite
> 
>     The last command will not just migrate the database but also adapt
>     akonadiserverrc accordingly.

Now we're back to system-wide again.  The outdent indicates that to some
degree and I'm of two opinions whether that needs to be made explicit or
not.  That's a judgement call.  But if so, one way (that I'm not entirely
satisfied with as it's arguably a bit informal/unprofessional sounding for
a news item) to indicate it would be:

+
+Now systemwide again.

> In order to keep using QMYSQL backend for users' existing Akonadi instances,

s/QMYSQL/the QMYSQL/

> ensure that USE=mysql is permanently[4] enabled for kde-apps/akonadi-config
> [and dev-qt/qtbase respectively].
> 
> In order to keep QMYSQL backend as default choice for new Akonadi instances,

s/QMYSQL/the QMYSQL/
s/default/the default/

> make sure that USE=sqlite is disabled for kde-apps/akonadi-config.
> 
>     Remember to run dispatch-conf (preferred) or etc-update to get updated
>     configuration files:

Do we really need to indicate dispatch-conf is preferred here?  IMO users
with sufficient gentoo history that this NEWS item applies to their systems
will already have a chosen default that works for them, and asserting that
one or another is "(preferred)" here only distracts from the purpose of the
NEWS item.

I'd thus suggest removing the "(preferred)" and omitting the
explicit dispatch-conf invocation that follows (and changing the : to a .).
The reminder on its own should be sufficient.  So:

Remember to run dispatch-conf or etc-update to get updated config files.

(Omit the following explicit dispatch-conf command.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Back to linux.gentoo.dev | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

  [gentoo-dev] [RFC] News Item: KDE PIM 26.04.1 default backend changes to  sqlite Andreas Sturmlechner <asturm@gentoo.org> - 2026-05-12 00:20 +0200
  [gentoo-dev] Re: [RFC] News Item: KDE PIM 26.04.1 default backend changes to sqlite Duncan <1i5t5.duncan@cox.net> - 2026-05-12 06:50 +0200
  Re: [gentoo-dev] [RFC] News Item: KDE PIM 26.04.1 default backend  changes to sqlite Marc Schiffbauer <mschiff@gentoo.org> - 2026-05-12 11:20 +0200
      Re: [gentoo-dev] [RFC] News Item: KDE PIM 26.04.1 default backend changes to  sqlite Andreas Sturmlechner <asturm@gentoo.org> - 2026-05-12 18:20 +0200
  Re: [gentoo-dev] [RFC] News Item: KDE PIM 26.04.1 default backend changes to sqlite Alexey Sokolov <alexey+gentoo@asokolov.org> - 2026-05-12 19:10 +0200

csiph-web