summaryrefslogtreecommitdiff
path: root/dev-qt/qtwebengine/qtwebengine-6.8.0_rc.ebuild
AgeCommit message (Collapse)Author
2024-10-08dev-qt/qtwebengine: drop 6.8.0_rcIonen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-24dev-qt/qtwebengine: fix build with USE=-vaapi in 6.8+Ionen Wolkens
Per the comment, already couldn't use system's libvpv when USE=vaapi is enabled (this is intentionally enforced by the build system rather than "broken"), and now USE=-vaapi fails to build in 6.8 with system's. Seems like an easy fix but (even if fixed) feel it would be simpler keep the same setup regardless of USE=vaapi until vaapi allows using system's. I hardly test USE=-vaapi and missed that it broke, and I assume this holds for upstream too. qtwebengine does keep bundled libvpx either up to date or backports security fixes, albeit bumps are less frequent and fixes could lag a bit (not that we had a choice with USE=vaapi either way, unless drop vaapi support). As a small perk, it'll spare users from rebuilding qtwebengine on libvpx subslot bumps which happen now and then. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-24dev-qt/qtwebengine: add 6.8.0_rcIonen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>