Please reconsider planned build breakage on new KF deprecations

[Ingo Klöcker]

On Mittwoch, 18. August 2021 16:27:29 CEST Friedrich W. H. Kossebau wrote:
> I wonder: who is in favour of the current approach? Who is not in favour?
> Could this be agreed on to be changed?

I'm in a different, but related situation.

I've been working a lot on libkleo and kleopatra for about a year now. I'm not 
building KF myself, but I'm using openSUSE Tumbleweed, so that I get the 
latest released KF a short time after the release. My problem is that the 
required KF version in PIM is increased too early, i.e. before openSUSE 
Tumbleweed provides the latest KF. Therefore, I'm patching the required KF 
version all of the time in libkleo and kleopatra. So far me requiring/building 
against an earlier version of KF has never broken my builds, so, apparently, 
the early increase doesn't seem to be necessary.

Therefore, I'm in favor of delaying the increase of the required KF version in 
PIM for a few more days after a new KF release, so that I (and other people 
working on PIM but not on KF) have a chance to get the new KF release from 
their rolling distribution before the new KF release is required by PIM.

I also support Friedrich and think that setting 
KF_DISABLE_DEPRECATED_BEFORE_AND_AT
to the currently released version of KF instead of the next version of KF 
should be sufficient for keeping PIM mostly clean of deprecated KF usage.

Given that there now is a "dev-disable-deprecated" CMake preset (since a few 
days in kleopatra and most likely also all other PIM projects), people who 
want to have disabled deprecations for their development workflow can easily 
get it. So, there's no need to make everybody else bleed, waste time and/or, 
most importantly, lose their motivation and mental power to work on PIM. (Yes, 
I saw that this preset disables all deprecated stuff for Qt 6 and KF 6. If 
needed, please add a CMake preset "dev-disable-deprecated-next-kf".)

tl'dr proposal:
* Increase the required version of KF for all PIM projects at least one week 
(7 days) after the release of a new version of KF instead of immediately after 
a new KF release.
* Set KF_DISABLE_DEPRECATED_BEFORE_AND_AT to the version of the latest 
released version of KF instead of the upcoming version of KF.

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20210818/d521f47c/attachment.sig>