portage and update sharing

[fuzzythebear]

This is what i want to accomplish :

I got two gentoo boxes : one is the gateway for the whole
network . Box is an athlon 1800 ,the other my work box
also an athlon 1800 same mobo as the gate.

Since i find it a heck of a waste of a finely working box i decided to start
using the gateway also as a distcc server . From my box i use both my
comp and the gate for compiles.Works fine. I also at the same time made it
the other way around so the gate could also use my workstation for the heck of it
That works fine .

My next step is a shared distfiles repo to save on the gateway's disk space
again no big deal i been told , just use NFS to share the directories .
Where im at a loss is that a friend , absent at the moment , told me that
i could use the built updates on both machines .. and that's where i dont
seem to find trace of a document on how to acheive this.

( Again .. it may exist im sure but i just havent found where yet )

Thing is .. both boxes dont have all the same programs installed in them.
There are differences .. ex the firewall that aint installed on the workstation.

How can this share be acheived ?
How do we tell the different boxes that the updates are already compiled ?
How do we tell the gate it's updates are on the workstation or the other way
around ?
How do we make sure even if the updates arent in the shares that then
the box should go ahead and compile it's own ?

Many questions ..

Im also interrested in harnessing more of the gate's power if it's possible
can we even talk clustering ( LOL ) in this case ?

The more i get out of that box the better it seems.. cpu at 1% use seems
a lot of waste : |

Ideas .. suggestions ? good uses for a perfectly fine gentoo
box sitting idle passing packets ?

Thanks for the suggestions : )

Fuzzy



``I guess I should warn you, if I turn out to be particularly clear, you've probably misunderstood what I said.'' A Greenspan

[fangorn]

[fuzzythebear]

ok so morale of the story .. => after several hours more
reading .. dang those eyes are a source of motivation ..

in the gateway add usepkg to FEATURES in make.conf
in the workstation .. add buildpkg to FEATURES in make.conf
add to the same in both
PORTDIR=/usr/portage
PKGDIR=${PORTDIR}/packages
export the workstations /usr/portage/distfiles and /usr/portage/packages
( sharing through NFS with the gate )
( more man pages and wild guesses, more questions but..yet .. those eyes..
create the /usr/portage/packages dir on both machines
clean out the /usr/portage/distfiles on the gate
mount directories to the same location ( /usr/portage/distfiles and packages )
on the gateway ( make fstab entries and mount )
that should be it .. probably is .. i hope ..

ric All # ls
eix-0.3.0-r1.tbz2
so the test pack built is here ..
now on the gate ..
It gets the source from the gateway .
still is building the app ..
maybe i misunderstand the tar.gz will still be compiled ?
what am i missing ?

then the question of how to prevent packs to use the prebuilt ones
where hardware dictates still is eluding me ..

Suggestions ?

Fuzzy

( Man .. those eyes and that look are an unexpected source of motivation ...

[fangorn]

This only works for pakets with the smallest common features. If you have compiled pakets for Pentium 4 you cannot run them on a Pentium 3 or Athlon XP machine. I dont know of a solution for packages for more than one architecture being shared over this.

[JSharku]

It should work that way yes, although I don't see a 'usepkg' option in /etc/make.conf.example

[Monkeh]

Set FEATURES=buildpkg on both machines, and when you emerge something on one machine, you can just emerge -K on the other. Just try not to get your USE-flags in a muddle.