On Friday, 25 October 2019 21:15:19 CEST, Friedrich W. H. Kossebau wrote:
Am Donnerstag, 24. Oktober 2019, 18:52:34 CEST schrieb laurent Montel:
Who told you that it will keep broken ?
If we show that it doesn't build we will fix it.
I don't see the problem. ...
The problem I see is availability of resources of people. And forcing them
into caring for deprecated API. This should be an opt-in for those happy to
work on deprecations once they appear.
It's especially annoying for packagers when testing new Qt versions. It's
just wasted time to backport patches for that with no real benefit at all.
I remember adding 30 patches (mostly to PIM packages) with one Qt update
just to keep stuff compileable and 5.14 needs a few of these again. So
please don't use -DQT_DISABLE_DEPRECATED_BEFORE=0x060000 at least with
releases. It's as bad as an idea like using -Werror with released code.
I see that some of these were added/moved behind an "if (EXISTS
"${CMAKE_SOURCE_DIR}/.git")" so this mail might become obsolete, hopefully.
Cheers,
Heiko
