https://techbase.kde.org/Development/Tools/Using_kconf_update#Debugging_and_testing
describes how to run repeated tests of kconf_update scripts in --testmode.
It is necessary to delete update group flags from kconf_updaterc,
which is inconvenient.

With this patch, kconf_update will not use kconf_updaterc when in --testmode,
so this step is no longer necessary.

Additionally, running all installed update scripts automatically
is no longer possible in --testmode, since that is probably only useful
if you have your home directory in ~/.qttest/config/.

I don’t expect problems, since this affects only --testmode, and the update group
flags are still present in the modified config files themselves.

See https://community.kde.org/Frameworks/Frameworks_Logging_Policy

Summary:
Convert license headers to SPDX statements and add
license files as required by REUSE specification.

Reviewers: cgiboudeaux

Reviewed By: cgiboudeaux

Subscribers: ognarb, cgiboudeaux, kde-frameworks-devel

Tags: #frameworks

Maniphest Tasks: T11550

Differential Revision: https://phabricator.kde.org/D27601

Summary:
In kconf_update, the ctime usage used to be about metadata change time
(buff.st_ctime, before it got ported to the misnamed created()).
I ported it to birthTime, because I think
date of birth is a more useful way to identify a file than
date of permission change which doesn't really matter to us.
But in practice, I can't help but wonder if mtime alone wouldn't be
enough.

For the QStringLiteral("%%1").arg(i) bit, I tested it in tst_qstring,
the first % is left untouched.

Test Plan: make && ctest

Reviewers: mdawson, arichardson, vkrause

Reviewed By: vkrause

Subscribers: pino, arojas, mlaurent, kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D23815

GIT_SILENT