On 09/12/2017 10:02 AM, Mike Gabriel wrote:
For the .deb packages, Debian-wise, I propose dropping wheezy support
and making sure that X2Go Client builds against Qt5 in Debian jessie
(afaik, that should be doable).
Wheezy is still supported through Debian LTS for the next year.
Alternatively, one could build-depend on Qt5 _or_ Qt4 in
debian/control, let the build script setup the build env (if Qt5 is
available, then pull-in Qt5, otherwise pull-in Qt4), then test what's
available and build against what's availeble via X2Go Client's Makefile.
I have a setup that automatically can depend upon a choice from debian/rules. It's hackishly, but so far has been working good to either build the MATE bindings against GTK+ 2 or 3.
I guess I will employ the same scheme here as well.
For RPM-based distros, the x2goclient.spec can be if-claused heavily
to support both build paths (Qt4 and Qt5).
Yeah, but there's no current RPM-based distro we still support that doesn't have Qt5, IIRC. We can switch to Qt5 unconditionally there I guess.
Mihai