On 12/10/25 10:16 AM, Dr Rainer Woitok wrote: > Greetings, > > since quite some time I'm speeding up "emerge" by installing plenty of > packages I do not set personal USE flags for from the binhost. This > worked well until June where package "sys-kernel/gentoo-sources-6.12.31" > was also provided by the binhost. While building the kernel packages > from source took 2 or 3 minutes on my rig, installing package "sys-ker- > nel/gentoo-sources-6.12.31" from the binhost took 12 minutes! In Sep- > tember I built package "sys-kernel/gentoo-sources-6.12.41" from source > (the binhost was still offering "sys-kernel/gentoo-sources-6.12.31") > which again took only 2 minutes. > > Currently the binhost is offering "sys-kernel/gentoo-sources-6.12.58" > and installing it from there again took 14 minutes while building it > from source took 2 minutes as usual. > > Can anybody shed some light on this (at least for me) unexpected behavi- > our?
Not sure why the merge time would be so long for a binary version. Regarding providing binpkgs of sys-kernel/*, we don't intentionally build them, but they are created as a side effect of building other packages that also have rdepend on e.g. a kernel module. Since the binhost cycles through "random" packages for extra coverage, packages can appear and disappear if not part of the base collection (kde, gnome, and a selection of popular apps). Relevant: https://github.com/gentoo/portage/pull/1527 -- configure binhost to prefer binaries or exclude them on a per package basis. https://bugs.gentoo.org/542480 -- teach build servers to not produce binpkgs for packages where it's worse than compiling from source. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
