Re: Requiring Qt 5.15 for KDE Frameworks 5?
> Are there any objections or concerns or potential release schedule conflicts > if we did that? Not from the Debian side. Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: Requiring Qt 5.15 for KDE Frameworks 5?
On Saturday, March 27, 2021 14:11 CET, David Faure wrote: > On samedi 27 mars 2021 12:51:37 CET Kai Uwe Broulik wrote: > > during the ongoing KDE Frameworks 6 sprint we were just contemplating > > whether we can bump the required Qt dependency for Frameworks 5 to Qt 5.15. > > While at it, can we also get your feedback on > * Requiring C++17 > * Requiring CMake >= 3.16 +1 on all 3 from OpenMandriva -- at least on our side, ancient releases that don't even get a modern compiler don't get desktop updates either. Releases that do get desktop updates also get updated Qt, cmake and friends. ttyl bero
Re: Requiring Qt 5.15 for KDE Frameworks 5?
On samedi 27 mars 2021 17:07:14 CET Nicolás Alvarez wrote: > > El 27 mar. 2021, a la(s) 12:30, Fabian Vogt > > escribió: Moin, > > > > Am Samstag, 27. M?rz 2021, 14:11:38 CET schrieb David Faure: > > On samedi 27 mars 2021 12:51:37 CET Kai Uwe Broulik wrote: > Hi everyone, > during the ongoing KDE Frameworks 6 sprint we were just contemplating > whether we can bump the required Qt dependency for Frameworks 5 to Qt > 5.15. > Reason being that Qt 5.15 includes a set of porting aids and > forward-compatibility with Qt 6, such as version-less "Qt" rather than > "Qt5" CMake target, various QStringView-related features, and so on. > We would like to start working on KDE Frameworks 6 on Qt 6 but still > keep Frameworks 5 supported with as little overhead as possible, i.e. > not having a gazillion ifdefs or even dedicated branch, which we would > likely need, should we have to continue supporting Qt 5.14 in the > process. > Are there any objections or concerns or potential release schedule > conflicts if we did that? > >> > >> While at it, can we also get your feedback on > >> * Requiring C++17 > > > > Which for GCC means at least g++ 9 in practice due to std::filesystem? > > I think we need to be more specific and say what is the minimum compiler > version. Maybe we can set g++8 as the minimum and use C++17 language > features while avoiding std::filesystem. > > But only if someone actually cares about keeping gcc8 support :) I'm pretty sure we can live without std::filesystem, given that we have QFile and KIO. I would actually find it confusing to see code that starts using a third subsystem for this, at least until proving that it's way better -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: Requiring Qt 5.15 for KDE Frameworks 5?
On Sat, Mar 27, 2021 at 12:41 PM Nicolás Alvarez wrote: > > > > El 27 mar. 2021, a la(s) 12:30, Fabian Vogt > > escribió: > > Moin, > > > > Am Samstag, 27. M?rz 2021, 14:11:38 CET schrieb David Faure: > > On samedi 27 mars 2021 12:51:37 CET Kai Uwe Broulik wrote: > Hi everyone, > during the ongoing KDE Frameworks 6 sprint we were just contemplating > whether we can bump the required Qt dependency for Frameworks 5 to Qt > 5.15. > Reason being that Qt 5.15 includes a set of porting aids and > forward-compatibility with Qt 6, such as version-less "Qt" rather than > "Qt5" CMake target, various QStringView-related features, and so on. > We would like to start working on KDE Frameworks 6 on Qt 6 but still > keep Frameworks 5 supported with as little overhead as possible, i.e. > not having a gazillion ifdefs or even dedicated branch, which we would > likely need, should we have to continue supporting Qt 5.14 in the > process. > Are there any objections or concerns or potential release schedule > conflicts if we did that? > >> While at it, can we also get your feedback on > >> * Requiring C++17 > > > > Which for GCC means at least g++ 9 in practice due to std::filesystem? > > I think we need to be more specific and say what is the minimum compiler > version. Maybe we can set g++8 as the minimum and use C++17 language features > while avoiding std::filesystem. > > But only if someone actually cares about keeping gcc8 support :) > I don't, not even for RHEL/CentOS 8 where GCC 8 is the default compiler. We can easily use GCC 10. I like std::filesystem too much to say no to it. :) -- 真実はいつも一つ！/ Always, there's only one truth!
Re: Requiring Qt 5.15 for KDE Frameworks 5?
> El 27 mar. 2021, a la(s) 12:30, Fabian Vogt escribió: > Moin, > > Am Samstag, 27. M?rz 2021, 14:11:38 CET schrieb David Faure: > On samedi 27 mars 2021 12:51:37 CET Kai Uwe Broulik wrote: Hi everyone, during the ongoing KDE Frameworks 6 sprint we were just contemplating whether we can bump the required Qt dependency for Frameworks 5 to Qt 5.15. Reason being that Qt 5.15 includes a set of porting aids and forward-compatibility with Qt 6, such as version-less "Qt" rather than "Qt5" CMake target, various QStringView-related features, and so on. We would like to start working on KDE Frameworks 6 on Qt 6 but still keep Frameworks 5 supported with as little overhead as possible, i.e. not having a gazillion ifdefs or even dedicated branch, which we would likely need, should we have to continue supporting Qt 5.14 in the process. Are there any objections or concerns or potential release schedule conflicts if we did that? >> While at it, can we also get your feedback on >> * Requiring C++17 > > Which for GCC means at least g++ 9 in practice due to std::filesystem? I think we need to be more specific and say what is the minimum compiler version. Maybe we can set g++8 as the minimum and use C++17 language features while avoiding std::filesystem. But only if someone actually cares about keeping gcc8 support :) -- Nicolás
Re: Requiring Qt 5.15 for KDE Frameworks 5?
Moin, Am Samstag, 27. M?rz 2021, 14:11:38 CET schrieb David Faure: > On samedi 27 mars 2021 12:51:37 CET Kai Uwe Broulik wrote: > > Hi everyone, > > > > during the ongoing KDE Frameworks 6 sprint we were just contemplating > > whether we can bump the required Qt dependency for Frameworks 5 to Qt 5.15. > > > > Reason being that Qt 5.15 includes a set of porting aids and > > forward-compatibility with Qt 6, such as version-less "Qt" rather than > > "Qt5" CMake target, various QStringView-related features, and so on. > > > > We would like to start working on KDE Frameworks 6 on Qt 6 but still > > keep Frameworks 5 supported with as little overhead as possible, i.e. > > not having a gazillion ifdefs or even dedicated branch, which we would > > likely need, should we have to continue supporting Qt 5.14 in the process. > > > > Are there any objections or concerns or potential release schedule > > conflicts if we did that? > > While at it, can we also get your feedback on > * Requiring C++17 Which for GCC means at least g++ 9 in practice due to std::filesystem? > * Requiring CMake >= 3.16 > > Obviously this only matters for distributions that update KF5 every month. AFAICT it will affect all distros at some point in the future, but those which update everything in a rolling manner should be fine anyway. openSUSE Tumbleweed is one of those and so it's not an issue. On Leap 15.x, the default compiler is GCC 7, so we'll have to switch to GCC9+ for that. That's fortunately fairly simple to do, so not really an issue either. Cheers, Fabian
Re: Requiring Qt 5.15 for KDE Frameworks 5?
On Saturday, 27 March 2021 14:11:38 CET David Faure wrote: > While at it, can we also get your feedback on > * Requiring C++17 > * Requiring CMake >= 3.16 > > Obviously this only matters for distributions that update KF5 every month. FreeBSD is fine with all of that, we track frameworks within a week or two, CMake similarly, and ship recent clang (or gcc 10 on platforms that clang doesn't support). [ade] signature.asc Description: This is a digitally signed message part.
Re: Requiring Qt 5.15 for KDE Frameworks 5?
On samedi 27 mars 2021 12:51:37 CET Kai Uwe Broulik wrote: > Hi everyone, > > during the ongoing KDE Frameworks 6 sprint we were just contemplating > whether we can bump the required Qt dependency for Frameworks 5 to Qt 5.15. > > Reason being that Qt 5.15 includes a set of porting aids and > forward-compatibility with Qt 6, such as version-less "Qt" rather than > "Qt5" CMake target, various QStringView-related features, and so on. > > We would like to start working on KDE Frameworks 6 on Qt 6 but still > keep Frameworks 5 supported with as little overhead as possible, i.e. > not having a gazillion ifdefs or even dedicated branch, which we would > likely need, should we have to continue supporting Qt 5.14 in the process. > > Are there any objections or concerns or potential release schedule > conflicts if we did that? While at it, can we also get your feedback on * Requiring C++17 * Requiring CMake >= 3.16 Obviously this only matters for distributions that update KF5 every month. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Requiring Qt 5.15 for KDE Frameworks 5?
Hi everyone, during the ongoing KDE Frameworks 6 sprint we were just contemplating whether we can bump the required Qt dependency for Frameworks 5 to Qt 5.15. Reason being that Qt 5.15 includes a set of porting aids and forward-compatibility with Qt 6, such as version-less "Qt" rather than "Qt5" CMake target, various QStringView-related features, and so on. We would like to start working on KDE Frameworks 6 on Qt 6 but still keep Frameworks 5 supported with as little overhead as possible, i.e. not having a gazillion ifdefs or even dedicated branch, which we would likely need, should we have to continue supporting Qt 5.14 in the process. Are there any objections or concerns or potential release schedule conflicts if we did that? Cheers Kai Uwe
