So there is no release date, as of yet for the next release of LXQt, but it looks like we're going to run into the same issue that the KDE team does. In so far as We're going to need to keep the Qt5 versions around, for leap, but have Qt6 from upstream for Tumbleweed. How do we want to approach this? Rename the packages that can't be co-installed to -qt5 and -qt6 variants? That's what I've done so far in X11:LXQt:qt6, but this isn't really a call I want to make on my own.
For context: https://lxqt-project.org/blog/2024/02/15/qt-6-and-wayland/
In so far as We're going to need to keep the Qt5 versions around, for leap, but have Qt6 from upstream for Tumbleweed.
Can we not just have Qt6 in X11:LXQt (and TW etc) and Leap will just get bugfixes for the old Qt5 versions?
On 2/19/24 00:37, Michael Vetter wrote:
For context: https://lxqt-project.org/blog/2024/02/15/qt-6-and-wayland/
In so far as We're going to need to keep the Qt5 versions around, for leap, but have Qt6 from upstream for Tumbleweed.
Can we not just have Qt6 in X11:LXQt (and TW etc) and Leap will just get bugfixes for the old Qt5 versions?
Ok, so as I understand it, and I'd be happy to be wrong, but basically in order for something to be *in* Leap it has to be *in* openSUSE:Factory Now, this may completely be a non-issue, in so far as I pushed the current 1.4 builds to openSUSE:Backports:SLE-15-SP6 so Lubos and Neal can get them into Leap 15.6 If there is a Leap 15.7, as I understand it, the odd numbered minor releases don't generally get version bumps, so no issue there. Leap 16 is far enough out, that LXQt 2.0 should be out, and be fully ported to Qt6. The only circumstance in which this becomes an issue, is if for some reason, the Upstream were to ship a 1.5 that were still Qt5 based, or if for some reason Qt6 didn't get into Leap 16 (which is unlikely) If we needed to support 1.x/Qt5 versions for Leap, and 2.0/Qt6 versions for Tumbleweed for any length of time, we'd need to keep lxqt-panel-qt5 and lxqt-panel-qt6 (or something similar) around in openSUSE:Factory to comply with policy, like KDE has to. I'm mostly just trying to get a feel for what direction we'd want to go (or just drop Leap altogether) if we run into one of these situations
participants (2)
-
Michael Vetter -
Shawn W Dunn