| 1 |
Volker Armin Hemmann wrote: |
| 2 |
> On Tuesday 23 September 2008, Alan McKinnon wrote: |
| 3 |
> |
| 4 |
>> |
| 5 |
>> You could even set up a mini- trimmed-down sync server. Put your master |
| 6 |
>> copies of stuff there, take steps so that portage doesn't nuke things, and |
| 7 |
>> set up a cron to sync once a day. Tell your machines to get their portage |
| 8 |
>> tree from this server, not gentoo.org somewhere and let rip. Also put a |
| 9 |
>> proxy on that sync server of yours so distfile downloads only happen once. |
| 10 |
>> There's many ways to do this - squid is obvious but I believe portage can |
| 11 |
>> do something similar (which I have not used myself) |
| 12 |
>> |
| 13 |
> |
| 14 |
> you can even put the compiling on one server and let the others download and |
| 15 |
> install the packets. AFAIR BINHOST is the thing to google for. |
| 16 |
> |
| 17 |
> |
| 18 |
> |
| 19 |
Oh yeah, the first server would be an rsync mirror, and the distfiles |
| 20 |
proxy, I've done both before, and both are easy enough. |
| 21 |
|
| 22 |
I hadn't considered the pkg thing, but it should be easy enough to set |
| 23 |
the buildpkg and usepkg features in the new profile, and nfs mount the |
| 24 |
packages directory..... |
| 25 |
|
| 26 |
The main thing I'm considering at the moment though is keeping the |
| 27 |
configuration consistant accross different servers, which the profile |
| 28 |
seems best set to solve... |
Archives