It looks like media-sound/qtractor supports both qt4 and qt5. Since qt4 is dead, please drop qt4 support and just enable qt5 unconditionally.
feel free to drop the flag
Came here from https://github.com/gentoo/gentoo/pull/5788. Already posted the same comment there, but also wanted to mention it here Enabling Qt5 on Qtractor means one has to enable Qt5 on all (lv2) plugins which use Qt as well, otherwise Qtractor crashes. Unfortunately the released versions of suil don't support Qt5 inside gtk, which means that enabling Qt5 would make those plugins useless in suil based hosts (like jalv). So I'd prefer to either wait until there's a new suil release or add a datestamped ebuild for suil from current master (which does support Qt5 inside gtk). Also Qtractor upstream still supports Qt4. Why not just keep the option?
(In reply to Simon from comment #2) > Came here from https://github.com/gentoo/gentoo/pull/5788. > Already posted the same comment there, but also wanted to mention it here > > Enabling Qt5 on Qtractor means one has to enable Qt5 on all (lv2) plugins > which use Qt as well, otherwise Qtractor crashes. > > Unfortunately the released versions of suil don't support Qt5 inside gtk, > which means that enabling Qt5 would make those plugins useless in suil based > hosts (like jalv). > So I'd prefer to either wait until there's a new suil release or add a > datestamped ebuild for suil from current master (which does support Qt5 > inside gtk). Sure, we can wait for a while, it's not particularly urgent. Thanks for the feedback. > Also Qtractor upstream still supports Qt4. Why not just keep the option? Qt 4 is dead and we (Qt team) have no intentions of starting a local fork to try and keep it alive. We're already seeing problems building it with newer libraries and compilers so want to remove it when we can. Investigating low hanging fruit (ie. packages that support both qt4 and qt5) for cleanup is a good way to start.
(In reply to Simon from comment #2) > So I'd prefer to either wait until there's a new suil release or add a > datestamped ebuild for suil from current master (which does support Qt5 > inside gtk). Please let us know when you got a response from suil upstream about a new release. Otherwise I'd say we throw a snapshot @ ~arch.
(In reply to Andreas Sturmlechner from comment #4) > Please let us know when you got a response from suil upstream about a new > release. Otherwise I'd say we throw a snapshot @ ~arch. I've received a response from drobilla, he expects to cut a release within the next two weeks, so even if it will be slightly longer it won't be a very long wait :)
If this works fine with suil-0.10.0 now I guess we can drop qt4 after all.
Thanks, Qt4 support removed in git commits d08d7f15fb125e6df0af0f291182637d873b5274 and bcf1d5102b2ad55fb6f2d39defc0b76bdf08e362
