Are your systems the same architecture and similar profiles? If so, then yes. It’s just a matter of enabling it and running the quickpkg command.
Otherwise, it’s a bit harder. You’ll be using cross compiler (if different architecture) and a chroot. You’ll have to setup the host to compile for the target systems whenever you do updates. The initial compile will take a while since it’ll compile basically everything.
I use a self hosted binhost so that I only compile on one of my devices, share with the rest. Works flawlessly.
Sounds like an awesome setup. I can’t quite let go of my illusory
-march=nativebenefits lol.I’m sure there are small benefits, but the benefits of the binhost are much cooler to me
Was it much of a pain to set up? I was hemming and hawing about distcc recently, but binhost sounds potentially better.
Are your systems the same architecture and similar profiles? If so, then yes. It’s just a matter of enabling it and running the quickpkg command.
Otherwise, it’s a bit harder. You’ll be using cross compiler (if different architecture) and a chroot. You’ll have to setup the host to compile for the target systems whenever you do updates. The initial compile will take a while since it’ll compile basically everything.
Cool; I’ll check quickpkg out
If recommend checking out the gentoo wiki on “binary package guide” or something like that. It explains quickpkg and everything else.