Re: Making a partition larger without affecting my OS.

On 3/16/26 11:18 AM, Dave Sizer wrote:
> 
> Thank you Dale, that insight is really helpful!
> 
> On Sun, 15 Mar 2026, Dale wrote:
> 
> [...]
>> I copy the binaries over and emerge those, no compiling for those.  This
>> way my updates are only going to be out of sync version wise for maybe
>> 20 to 30 minutes or even less in a lot of cases.  Usually when I start
>> emerging the binaries, I start closing programs so that I can logout and
>> back in anyway.  It takes me a few minutes to close certain things and
>> make notes of something I need to get back to when I log back in.
> 
> Is there any doc or anything about how to emerge the binaries that were
> built in the chroot? Or would you mind giving me a quick writeup of the
> commands you use? Mostly curiosity, I'm always trying to learn more about
> the interals of Gentoo :)


emerge --getbinpkg (pull binaries from the internet via the official
binhost) implies --usepkg.

emerge --usepkg uses built binaries in /var/cache/binpkgs. So, bind
mount this directory into your chroot and emerge @world in the chroot --
it will build lots of bins -- then emerge outside the chroot and it will
reuse those bins.

A binkpg is always equivalent to compiling from source, unless the
ebuild was already buggy and changed behavior without using USE flags.
emerge --usepkg respects your USE flags.

The exception is CFLAGS, binaries are built for the official binhost
with generic flags in two tiers ("all amd64" and "recent amd64 with the
v3 micro-arch group of CPUs") but -march=native may be a bit faster (not
counting how slow it is to compile in the first place).



-- 
Eli Schwartz

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCabmzagUDAAAAAAAKCRCEp9ErcA0vVyGU
AQDVn9L000RUyop7qQtNKWTyDKkzDsjEWiOieyXIyOC9mgD9GQMbT3PNkHa1HqLVbyQh3rdBA3Nt
DBqha0OxANKh2gQ=
=I5uF
-----END PGP SIGNATURE-----