ein Server emerged, hat dabei die buildpkg Option gesetzt. Danach läßt man die anderen Server beim ersten die Pakete abholen und installiert die.

Für dich, aus man emerge:
--buildpkg (-b)
Tells emerge to build binary packages for all ebuilds processed
in addition to actually merging the packages. Useful for main-
tainers or if you administrate multiple Gentoo Linux systems
(build once, emerge tbz2s everywhere). The package will be cre-
ated in the ${PKGDIR}/All directory. An alternative for
already-merged packages is to use quickpkg which creates a tbz2
from the live filesystem.

--buildpkgonly (-B)
Creates binary packages for all ebuilds processed without actu-
ally merging the packages. This comes with the caveat that all
build-time dependencies must already be emerged on the system.
--getbinpkg (-g)
Using the server and location defined in PORTAGE_BINHOST (see
make.conf(5)), portage will download the information from each
binary package found and it will use that information to help
build the dependency list. This option implies -k. (Use -gK
for binary-only merging.)

-usepkg (-k)
Tells emerge to use binary packages (from $PKGDIR) if they are
available, thus possibly avoiding some time-consuming compiles.
This option is useful for CD installs; you can export
PKGDIR=/mnt/cdrom/packages and then use this option to have
emerge "pull" binary packages from the CD in order to satisfy
dependencies.