kconfig.git, branch v5.66.0-rc1

GIT_SILENT Commit translations from l10n-kf5

2020-01-04T10:04:46+00:00

GIT_SILENT Upgrade ECM and KF5 version requirements for 5.66.0 release.

2020-01-03T23:10:13+00:00

Remove endl at the end of qdebug

2020-01-03T06:28:43+00:00

GIT_SILENT Upgrade Qt5 version requirement to 5.12.0.

2019-12-21T11:32:31+00:00

Port deprecated methods

2019-12-19T12:39:34+00:00

GIT_SILENT Upgrade KF5 version to 5.66.0.

2019-12-14T11:06:58+00:00

kconfig EBN transport protocol cleanup

2019-12-11T09:09:50+00:00

Summary: Change and test transport protocol from http to https while correcting dead link

Reviewers: apol

Reviewed By: apol

Subscribers: kde-frameworks-devel

Tags: #frameworks

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

update @since

2019-12-10T11:33:16+00:00

Expose getter to KConfigWatcher's config

2019-12-10T11:15:11+00:00

Summary:
It can help save users having to member variables for the config and the
watcher.

Reviewers: broulik

Reviewed By: broulik

Subscribers: broulik, kde-frameworks-devel

Tags: #frameworks

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

Fix writeFlags with KConfigCompilerSignallingItem

2019-12-10T08:41:47+00:00

Summary:
KConfigCompilerSignallingItem both inherits KConfigSkeletonItem and
internally is powered by a separate KConfigSkeletonItem

The generated code calls setWriteFlags on the outer
KConfigCompilerSignallingItem instance, but the real writing is
performed by the internal version. We need to set the flags in the right
place.

Ideally we would do this in an overload of KConfigSkeletonItem, but
given we can't, I've shadowed the method. This isn't pretty, but given
the docs say it should generally only be used from auto generated code,
should be fine.

Test Plan: Used in workspace KCM

Reviewers: ervin

Reviewed By: ervin

Subscribers: kde-frameworks-devel

Tags: #frameworks

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