kossebau added a comment.
Be aware that just adding a plain KRUNNER_DEPRECATED is not up-to-modern KF standards :) Please see cf5f7b4040a77ae69452d58bc189dcc3baaedd92 <https://phabricator.kde.org/R308:cf5f7b4040a77ae69452d58bc189dcc3baaedd92> what macros there are now and how to apply them. Note especially the difference between the ENABLE (for declarations, visible both to library and 3rd-party API users) & BUILD (visible only to library)), as well as that 5.0 can be only used in the API dox text, the macros need the version where the deprecation tags are first used/released with, to be backward-compatible for library consumers which use the KF_DISABLE_DEPRECATED_BEFORE_AND_AT control macro. Please see also https://community.kde.org/Policies/Library_Code_Policy#Deprecation_of_API for general info about API deprecation in KF. REPOSITORY R308 KRunner REVISION DETAIL https://phabricator.kde.org/D29281 To: alex, #plasma, broulik, davidedmundson, vkrause Cc: kossebau, kde-frameworks-devel, LeGast00n, cblack, michaelh, ngraham, bruns
