Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#72538 - Use Qt5 rather than Qt6 for GPXSee builds

Attached to Project: Community Packages
Opened by Martin Tůma (tumic) - Monday, 25 October 2021, 11:10 GMT
Last edited by Toolybird (Toolybird) - Monday, 15 May 2023, 04:41 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Laurent Carlier (lordheavy)
Balló György (City-busz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

GPXsee is now compiled against Qt6 in Archlinux which is supported, but has various limitations when compared to Qt5 builds:

* The look&feel does not comply with the system look&feel as KDE still uses Qt5 and there is no Qt6 KDE style at the moment.
* Qt6 builds do not support other encodings than UTF-X in XML files and East Asian encodings in Garmin file formats.

Please switch the build back to Qt5, at least until KDE switches to Qt6.
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 15 May 2023, 04:41 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Cannot see this changing now at this late stage...
Comment by Antonio Rojas (arojas) - Monday, 25 October 2021, 16:24 GMT
* The look&feel does not comply with the system look&feel as KDE still uses Qt5 and there is no Qt6 KDE style at the moment.

I don't think this is a valid reason to use a deprecated toolkit when a maintained one is supported. The KDE Qt6 style is still very far away (KDE frameworks porting to Qt6 hasn't even started yet) and we're not going to hold back using Qt6 in all our packages until it happens.

* Qt6 builds do not support other encodings than UTF-X in XML files and East Asian encodings in Garmin file formats.

Do you have an upstream report for this?
Comment by Martin Tůma (tumic) - Monday, 25 October 2021, 19:55 GMT
> Do you have an upstream report for this?

It's not a bug, it's a feature... Qt6 intentionally dropped support for encodings different than UTF.
One could use QTextCodec from the Qt5Compat module to solve the Garmin files format issue, but Qt5Compat
will be dropped somewhere in the future anyway. For the XML encodings issue, there is however no other
solution than to use a XML parser outside of Qt. And that's something the author of GPXSee definitely
won't do, I can guarantee it to you as it is me ;-)

So apart from some crazy/hack solutions there is only the chance to use Qt5 as long as possible and hope
the non-UTF encodings will be almost death at that time. Qt thinks this already happened, but I don't think
so. In the Garmin world the non-UTF encodings even gained a massive popularity in the last time as Garmin
disabled UTF8 maps on their devices to prevent people from creating their own OpenStreetMap maps...

So while it is clear to me that you won't keep Qt5 alive in Archlinux eternally only because of a minor
package like GPXSee, it makes no sense to switch to Qt6 today. Qt6 brings no benefits to GPXSee at the moment,
it only has the presented drawbacks. That's why I suggest to postpone the switch at least until there is
KDE based on Qt6.
Comment by Martin Tůma (tumic) - Sunday, 31 October 2021, 16:45 GMT
The GPXSee Qt6 build uses the core5compat module to support the East Asian encodings where possible as of version 9.11. In XML files, still only the UTF family is supported (some more related info in QTBUG-86437) and the look&feel is of course still not optimal in KDE. But those two issues are common for all Qt6 applications at the moment...

Loading...