This reverts commit 8388ed0603f0d04d7adde2152b077dbd29275ee3.
The commit was only a workaround for neon shipping a broken tarball.
KDE Connect |
This reverts commit 8388ed0603f0d04d7adde2152b077dbd29275ee3.
The commit was only a workaround for neon shipping a broken tarball.
Revert untested, but it worked fine before the commit got merged.
No Linters Available |
No Unit Test Coverage |
Buildable 4939 | |
Build 4957: arc lint + arc unit |
I'm wondering whether the .protocol to .json conversion is related, because it was part of the same commit.
If not, I'll just revert the QCoreApplication change.
Is there some disadvantage to keeping things the way they are? From my understanding of the situation, having plugins instantiate a QApplication object is the way KIO wants things to be done (even though the particular commit which caused older plugins to break was a mistake that they have fixed). The .protocol file instead of the .json definitely seems to be the new way as well.
Indeed, I just read the commit message in kcrash:
The right fix is to create a QCoreApplication in all kioslaves
So other than the wrong subject there's nothing against this commit anymore.
Sorry for the noise.