FS#76769 - [chromium] Build with Qt5 support
Attached to Project:
Arch Linux
Opened by Emil (xexaxo) - Wednesday, 07 December 2022, 14:37 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 14 December 2022, 08:57 GMT
Opened by Emil (xexaxo) - Wednesday, 07 December 2022, 14:37 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 14 December 2022, 08:57 GMT
|
Details
Description:
Chromium 108 features a Qt5 backend, which can be used instead of the GTK3 one. Our current maintainer Evangelos Foutras (hats off for all the amazing Arch work, bug reports and fixes that you've contributed upstream) is aware of that and deferring enablement to a later date [1]. May I ask why, can we enable it? AFAICT the option is an explicit opt-in, so by default it will not change anything for the end-users. Happy to do some testing, or otherwise, if that would help. [1] https://github.com/archlinux/svntogit-packages/commit/4de5019014aeb77187a517c5ca6db8723d622a40 Additional info: * package version(s) chromium 108.0.5359.94-2 Steps to reproduce: * install chromium * open `chrome://settings/appearance` * look for the Qt Theme |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Wednesday, 14 December 2022, 08:57 GMT
Reason for closing: Implemented
Additional comments about closing: chromium 108.0.5359.124-1
Wednesday, 14 December 2022, 08:57 GMT
Reason for closing: Implemented
Additional comments about closing: chromium 108.0.5359.124-1
More importantly - the qt5 dependency should be an optdepents, since by default it's not used nor required. Hence it won't be installed for people who don't want to use it.
- building with qt5 support, and
- building _without_ gtk3 support
I think the former makes sense to initiate now. The latter would be nice, but it's a non-goal for the time being.
In the future it's possible that Gtk3 can be turned into an optdep (along with qt5-base) and Chromium should be able to use the appropriate toolkit based on the desktop environment it's launched in.