kconfig.git/autotests, branch v5.35.0 hurd kconfig.git tests: use QIODevice::Text in kconfigcompiler_test 2017-05-25T22:57:35+00:00 Pino Toscano pino@kde.org 2017-05-25T22:57:35+00:00 1fad6902629191558e53ea9b58a8a67a0bfc9440 This way, different newline endings in OSes are handled as \n when reading, and thus fixing the comparison on non-\n OSes. 
This way, different newline endings in OSes are handled as \n when
reading, and thus fixing the comparison on non-\n OSes.
tests: use right QProcess API in kconfigcompiler_test 2017-05-25T22:40:20+00:00 Pino Toscano pino@kde.org 2017-05-25T22:40:20+00:00 97ec146bd109109ac11e3c573625b47bfa4fd4ff Use the QProcess::start() variant with explicit (empty, in this case) arguments, so the program string is not parsed as shell command, thus preserving paths with spaces as such. 
Use the QProcess::start() variant with explicit (empty, in this case)
arguments, so the program string is not parsed as shell command, thus
preserving paths with spaces as such.
Fix relativePath calculation in KDesktopFile::locateLocal() 2017-04-25T21:37:11+00:00 Wolfgang Bauer wbauer@tmo.at 2017-04-25T21:37:11+00:00 3ad00c4e56eb9fe6ea7386f8ca1db6e15c26ac11 The "dir" and "path" variables were obviously swapped here by mistake. This resulted in the relativePath always being empty, and made the function return "~/.local/share/" (or "~/.config/") instead of the correct path. BUG: 345100 FIXED-IN: 5.34.0 Differential Revision: https://phabricator.kde.org/D5502 
The "dir" and "path" variables were obviously swapped here by mistake.
This resulted in the relativePath always being empty, and made the
function return "~/.local/share/" (or "~/.config/") instead of the
correct path.

BUG: 345100
FIXED-IN: 5.34.0
Differential Revision: https://phabricator.kde.org/D5502
Fix linking on Windows: don't link kentrymaptest to KConfigCore. 2017-02-04T17:46:24+00:00 David Faure faure@kde.org 2017-02-04T17:46:24+00:00 3cb4c615990b52d40564281a862b4e5a19fc7a1c It's not needed, this is purely a test for the standalone KEntryMap class. 
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 Stephen Kelly steveire@gmail.com 2017-02-04T09:45:19+00:00 36e17c3d1c6a2b6af6cb7bb7330cb34b459b25fd It is internal. 
It is internal.
Don't link against kconfigdata.cpp in the kentrymaptest unit test. 2017-02-04T07:51:06+00:00 Matthew Dawson matthew@mjdsystems.ca 2017-02-04T07:51:06+00:00 b939b48f8d5e5eaf9a51a7e9bda2ad8cedca27d9 Due to eab822e206207c51d47f0f0da109caacfbee4e2f, KEntryMap is now an exported type. As such it is no longer needed to link in kconfigdata.cpp into this test. 
Due to eab822e206207c51d47f0f0da109caacfbee4e2f, KEntryMap is now an
exported type.  As such it is no longer needed to link in kconfigdata.cpp
into this test.
Prefer nullptr over Q_NULLPTR 2017-01-16T17:17:34+00:00 Kevin Funk kfunk@kde.org 2017-01-16T17:17:34+00:00 2034e3ce7593f04d251b634bfe2d71b30f15ea3a 






Add python bindings
2017-01-15T11:48:23+00:00

Stephen Kelly
steveire@gmail.com

2017-01-15T11:36:08+00:00

51410384458b941291f71400d49c3f6d6efbef49












autotest: add expected failure with Qt 5.8.0, with runtime check.
2017-01-09T08:34:25+00:00

David Faure
faure@kde.org

2017-01-09T08:34:25+00:00

be2b115e2467a224140125ec15ae5090e573fea5

+ simplify using recursive-remove and testmode.





+ simplify using recursive-remove and testmode.







This should now use nullptr
2017-01-08T16:23:38+00:00

David Faure
faure@kde.org

2017-01-08T16:23:38+00:00

d3de5a2a79d2786207d0cfbbc9828e00dabd148d