* Under the hood runs Chromium 87.0.4280.144 with security fixes up to version 96.0.4664.110 and patches were taken from of www/chromium 87.0.4280.141 (391acded85d8). * Prune some unneeded patches and and try to align the unbundling of dependencies similar to www/qt6-webengine for consistency.
Details
- Reviewers
- None
- Group Reviewers
kde - Commits
- R11:8067206f03a2: www/qt5-webengine: Update to 5.15.8
Building:
- Poudriere -> OK (12.3-, 12.4- 13.1-RELEASE, 14.0-CURRENT@8c309d48aab amd64 i386 ALSA/PULSE/SNDIO with/without DEBUG)
- If someone(tm) can run a test build on a aarch64 Platform that would be great.
Runtime:
- Tests with following consumers looked fine so far:
- www/dooble
- If someone(tm) can do further tests with other consumers and KDE applications that would be great.
Following features were tested with www/dooble
- Webcam
- Working multiple tabs, running videos in background tab
- Running WebGL via hardware acceleration
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
- Rebase
- Clean up some comment remnants that were added due debugging purposes
Ping? In the meantime, had anyone else of kde@ been able to test this diff of www/qt5-webengine a bit with some consumers?
I of course did not read a single patch in files/ :).
But I trust you made sure it works fine.
sorry for the silence -- I generally assume that your patches work :D
I'll rebuild my repo with it, and will see whether kmail works tomorrow.
This is understandable, because in files/ lurk several dangers. :)
Ping? In the meantime, had anyone else of kde@ been able to test this diff of www/qt5-webengine a bit with some consumers?
sorry for the silence -- I generally assume that your patches work :D
I'll rebuild my repo with it, and will see whether kmail works tomorrow.
No worries and thank you for the feedback. :)
My only concern was that www/qt5-webengine can be cross-checked for runtime by someone else, to avoid the kind of silly glitches that happened with www/qt6-webengine due a hardcoded path that was overlooked.
If I still hadn't heard anything after the ping, I'd have set the next weekend as an ETA to finally get this diff into the ports tree. :D
P.S.: Regarding the aarch64 platform I cannot give an info if its buildable. Presumably, someone will have to adjust some patches afterwards.
so far I did not notice any issue in kmail
Perfect, thanks for your help! I'm going to commit it in a few minutes. :D