kconfig.git, branch v5.32.0-rc1

Commit translations from l10n-kf5

2017-03-04T16:08:53+00:00

Upgrade ECM and KF5 version requirements for 5.32.0 release.

2017-03-03T12:45:04+00:00

KConfig: stop exporting and installing KConfigBackend.

2017-02-20T23:17:01+00:00

Summary:
It can't possibly have been used anywhere, because it's not in the KConfig
API anywhere. The intended way to use this API was by providing a plugin
that would derive from KConfigBackend but the plugin loading code
in KConfigBackend::create has been disabled since before KF 5.0.

The reason I want to stop exporting this class is to be able to
optimize it (e.g. the QDateTime in it is completely unused but leads
to data races due to tzset)

Test Plan: Note, I'll rename it to _p.h if we agree, it would just have made this diff too big.

Reviewers: mdawson

Reviewed By: mdawson

Subscribers: #frameworks

Tags: #frameworks

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

GIT_SILENT remove comment about this being a temp workaround.

2017-02-14T06:54:55+00:00

Even with 5.8 we need it, not due to QLockFile, but just due to mainConfigName(),
see unittest ksharedconfig_in_global_object

Upgrade KF5 version to 5.32.0.

2017-02-11T10:10:06+00:00

Upgrade ECM and KF5 version requirements for 5.31.0 release.

2017-02-04T18:08:40+00:00

Fix linking on Windows: don't link kentrymaptest to KConfigCore.

2017-02-04T17:46:24+00:00

It's not needed, this is purely a test for the standalone KEntryMap class.

Don't export KEntryMap

2017-02-04T12:50:26+00:00

It is internal.

Don't link against kconfigdata.cpp in the kentrymaptest unit test.

2017-02-04T07:51:06+00:00

Due to eab822e206207c51d47f0f0da109caacfbee4e2f, KEntryMap is now an
exported type.  As such it is no longer needed to link in kconfigdata.cpp
into this test.

Upgrade Qt5 version requirement to 5.6.0.

2017-02-02T09:25:15+00:00