aboutsummaryrefslogtreecommitdiff
path: root/src/kconf_update/README.kconf_update
AgeCommit message (Collapse)Author
2019-03-26point readme to the wiki pageHarald Sitter
Summary: the wiki page says the readme is duplicated into the wiki. so, what we end up with is either - they end up out of sync - someone gets real angry because the wiki needs format markup while the readme must not have markup - someone doesn't get angry and simply copies either markup or nomarkup to the respectively unsuitable target it's an unsustainable situation... so instead let's point the readme to the wiki and consider that the place where the documentation is maintained Subscribers: kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D19779
2015-02-14Revert "Revert the SIC in commit 915976c1238be811f169eab1b02f7e8dad6410e0."Matthew Dawson
This reverts commit 9eee15917e01a89d937d1cba2eebbe9d65daeb72. As agreed with David Faure, we are going to leave this change in place for 5.7 and see what happens. CCMAIL: faure@kde.org CHANGELOG: Reverts previous commit, both can be left out of the changelog.
2015-02-14Revert the SIC in commit 915976c1238be811f169eab1b02f7e8dad6410e0.Matthew Dawson
On further reflection, introducing a SIC to fix the bug is not ideal. I'm working on something that will address the underlying bug, but I didn't have it in time for 5.7. The versioning behaviour is left, as I do want it to exist for the future. This only reverts the mandatory versioning of files to avoid the compatibility break. CHANGELOG: Undo 915976c123, which never saw a release, enough to avoid the SIC.
2015-01-06Don't upgrate config file with upd file from kde4.Montel Laurent
This patch is necessary because: When we use kf5 + kde4 application, kconf_update which launchs at the start when we launch kde. But it will migrate some config file, for example it will show that we need to migrate konversation so it will create a konversationrc in .config/ But when we launch konversation there is a kdelibs4migrator which wants to migrate settings and config in .config but it shows a konversationrc in .config so it will never migrate and we will lose all settings. So we can force to remove all .upd in kf5 but it will not fix problem during migration or when we have kde4 application install in same directory as kf5. So now I force for each upd file to have a "Version=5" so kconf_update (kf5) will migrate just kf5 upd file and it will fix my bugs. REVIEW: 121797 CHANGELOG: Now kconf_update doesn't process upd file from kde4. We need to add "Version=5" in top of the upd file otherwise it will be skipped.
2013-12-18Move kconfig code to the root directory.Jenkins CI