Peter,
On Monday, 2026-02-16 16:31:01 +0000, you wrote:
> ...
> If I 'emerge -av qtwebengine' it fetches the binary
> package as expected, but if I go to emerge something that depends on
> qtwebengine, portage wants to recompile it, not fetch the binary, even
> though the existing version is the same.
The version is the same, yes, but the USE flags required by "something"
for "qtwebengine" most probably are not exactly those provided by the
binhost. As of yesterday evening the binhost provided two instances for
"qtwebengine" with two different sets of activated USE flags:
=dev-qt/qtwebengine-6.10.1 abi_x86_64 alsa amd64 bindist elibc_glibc
jumbo-build kernel_linux opengl pdfium pulseaudio qml screencast system-icu
vulkan widgets
=dev-qt/qtwebengine-6.10.1 abi_x86_64 alsa amd64 bindist elibc_glibc
jumbo-build kernel_linux opengl pdfium qml system-icu vulkan widgets
If your package "something" requires some of these activated USE flags
to be deactivated or requires additional activated USE flags, your only
chance is to modify the USE flags for package "something" so it stops
requiring a USE flag combination for package "qtwebengine" which is not
provided by the binhost.
Use "emerge -pv something" to find the USE flags package "something" re-
quires for package "qtwebengine" and use
eix --care --category-name --nocolor --verbose \
--versionsort --versionlines "something" > /tmp/"something".dep
to retrieve a longish list of both, unconditional and USE flag dependent
dependencies for the various supported versions of package "something".
Open the output file in your editor, search for the correct version of
package "something" and then search for "qtwebengine" to find out what
USE flag for "qtwebengine" is triggered by which USE flags for "some-
thing".
Been there, done that. Before I started using binary packages on my
laptop building package "qtwebengine" took around 6:15 hours :-(
So: good luck :-)
Sincerely,
Rainer
