| 1 |
Are the computers on a local network? |
| 2 |
Then doing this is very simple: |
| 3 |
nfs export /usr/porgat on your server (the build machine) |
| 4 |
nfs mount that on all other machines... |
| 5 |
|
| 6 |
This way yu can: |
| 7 |
1. emerge sync from any machine (you will update the same *central* db) |
| 8 |
2. emerge --buildpkg ... on your server |
| 9 |
3. emerge --usepkg on all your clients... |
| 10 |
(or you can even do build anywhere or in parallel (provided packageds do not |
| 11 |
collide of course)) |
| 12 |
|
| 13 |
If nfsmount is undesirabble, well, there are different networked filesystems, |
| 14 |
or you can script something along these lines employing rsync and/or scp (and |
| 15 |
this may work well even if comp'yuters are on different networks far away - |
| 16 |
namely if latency/throughput make network mounting undesirable). |
| 17 |
|
| 18 |
Another option is to use distcc which will distribute compilation effort among |
| 19 |
many computers (well, best resualts are provided by parallel use of both |
| 20 |
approaches...). |
| 21 |
|
| 22 |
George |
| 23 |
|
| 24 |
|
| 25 |
On Wednesday 12 March 2003 08:02, Michael Boman wrote: |
| 26 |
> I want to setup a local binary Gentoo mirror so my machines doesn't need |
| 27 |
> to compile the packages themself (get pre-compiled software) and also |
| 28 |
> only get software that has been tested on the particular hardware (the |
| 29 |
> 'client' machines are all the same hardware spec, except memory and cpu |
| 30 |
> speed, so CFLAGS are not changed.. and my USE flags are also same across |
| 31 |
> the machines. What I've figured out is: |
| 32 |
> |
| 33 |
> - I need to assign a machine to be a "auto-builder", just build everything |
| 34 |
> I want/need as pre-compiled packages |
| 35 |
> - I need a repository to store the packages |
| 36 |
> - Need to setup some kind of mirror I can point the other machines to |
| 37 |
> for their rsync mirror |
| 38 |
> - Make sure that the machines only uses the local repository for packages, |
| 39 |
> and always get the pre-compiled version of it |
| 40 |
> |
| 41 |
> Anyone have done some doc's to accomplish this? Where can I find those |
| 42 |
> if they exist? |
| 43 |
> |
| 44 |
> Also, is it possible to tell emerge to use another root (/) |
| 45 |
> when installing new packages, or is 'chroot' the |
| 46 |
> only option? I am experimenting with Solaris live |
| 47 |
> upgrade methology and want portage to update the cold |
| 48 |
> partition. http://www.samag.com/documents/s=7789/sam0302j/0302j.htm has |
| 49 |
> a description how Sun's Live upgrade works. |
| 50 |
> |
| 51 |
> Best regards |
| 52 |
> Michael Boman |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-dev@g.o mailing list |
Archives