Troy Dawson wrote:
> The biggest reason for building it as a module is the qt5 packages in
> RHEL8. If RHEL8 didn't have any of those, then I would completely agree
> with you.
To be honest, I am not convinced that replacing RHEL's Qt 5 (and making that
a requirement for the KDE software stack) is a good idea. It will break at
least some Qt applications in RHEL itself (unless the module rebuilds them
too) and some third-party ones (and you cannot rebuild those). While Qt is
backwards-compatible in principle (so you can often get away with just
upgrading it), please be warned that everything relying on private APIs WILL
break if not rebuilt (and there is a bunch of offenders there,
unfortunately), and some other applications might break due to behavior
changes. (Looking at what rebuilds get bundled with Fedora Qt upgrades may
give you a hint at affected packages. But of course it won't include
anything proprietary or otherwise third-party.)
I think it may be better to stick to whatever can be built with RHEL's Qt
5.11.x and the EPEL QtWebEngine 5.12.x that I helped you build. Upgrading to
QtWebEngine 5.12.x LTS security releases should be safely possible. (Please
do that!) For RHEL stuff, let RH deal with security. Hopefully, they will
eventually include a newer Qt in an update release.
Kevin Kofler
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
