Engine 6.11.2-7

QtWebEngine 6.11.2 with Omaweb's patch series applied, for Linux x86_64 and aarch64.

This is the engine Omaweb runs on, and it is a modified QtWebEngine. It installs into /usr/lib/omaweb and does not replace the distribution's qt6-webengine, so every other Qt application on the machine keeps the engine it had.

What changed since engine-6.11.2-6. The engine's code is the same: QtWebEngine 6.11.2 on Chromium 140.0.7339.225, with the same twenty patches. No security fix comes with this release.

• 6.11.2-6 for x86_64 was built against Qt 6.12 and required qt6-base and qt6-declarative 6.12.0 or newer. Omarchy machines install from Omarchy's stable mirror, which is still on Qt 6.11.2, so pacman could not install it there, and held Omaweb 0.13.0 back with it (Omaweb's #674).
• This release is built against the Qt Omaweb's readers have: Omarchy's stable mirror on x86_64 and Arch Linux ARM on aarch64, both Qt 6.11.2. Neither package names a Qt version. An engine built against Qt 6.11.2 runs on 6.12 too, and was checked there.
• aarch64 is the same build as 6.11.2-6, which was already built against Qt 6.11.2, repackaged under the new release number.

Corresponding source. The base is Qt's released qtwebengine-everywhere-src-6.11.2.tar.xz, which carries the Chromium tree it builds. The changes are the twenty patches in patches/ of omaweb-qtwebengine-patches at 504dc51, each a single commit with its own reasoning, and on x86_64 toolchain/clang.patch, which changes how the engine is compiled and not what its code does. packaging/MODIFICATIONS.md in the package says the same and ships with it, alongside the LGPL-3.0 text and Chromium's own notice taken from the tree the engine was built from.

The signed copy lives in Omaweb's pacman repository, which is where a reader gets it. The packages here are unsigned, and they are the artifacts the publishing workflow signs.

What it was tested against.

• verify-x86_64.txt and verify-aarch64.txt are the gate from the builds these packages carry. Each read V8's ninja file and found it compiled with its write barriers, then passed 37 of 37, 10 of 10, 3 of 3 and 1 of 1. Neither container had a stock engine, so the stock comparison was skipped.
• x86_64 was built with clang, LLD, ThinLTO and Chrome's PGO profile in an Arch container on a Ryzen 7 PRO 7840HS, installing from Omarchy's stable mirror (qt6-base 6.11.2-3). Each package holds 599 files.
• The x86_64 package was installed in fresh containers on Omarchy's stable mirror (Qt 6.11.2) and on Arch's current mirror (Qt 6.12.0). On both, Omaweb's engine contract suite passed 220 of 220, including the offscreen-document test for #646. Its 18 binaries need no Qt symbol newer than 6.11.