| 1 |
On Fri, 18 Jan 2008 11:17:32 +0100 (CET) |
| 2 |
Helmut Jarausch <jarausch@××××××××××××××××.de> wrote: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> I haven't found out how to teach emerge to rsync |
| 7 |
> /usr/portage/packages |
| 8 |
> as well. |
| 9 |
> Both, /etc/rsyncd.conf on the server and |
| 10 |
> /etc/portage/rsync_excludes |
| 11 |
> |
| 12 |
> only exclude distfiles. |
| 13 |
> |
| 14 |
> There is no server problem, since an |
| 15 |
> rsync on the command line does fetch |
| 16 |
> packages, too |
| 17 |
> |
| 18 |
> Many thanks for a hint, |
| 19 |
> |
| 20 |
> Helmut Jarausch |
| 21 |
> |
| 22 |
> Lehrstuhl fuer Numerische Mathematik |
| 23 |
> RWTH - Aachen University |
| 24 |
> D 52056 Aachen, Germany |
| 25 |
|
| 26 |
|
| 27 |
For sure "emerge --sync" calls rsync with "--exclude packages" and I |
| 28 |
don't know a "legal" way to change this behaviour. |
| 29 |
|
| 30 |
If all you want is just to compile on one system and distribute |
| 31 |
the compiled packages elsewhere through the network, there are two |
| 32 |
methods that worked here with no problems: |
| 33 |
|
| 34 |
1) export "packages" via nfs |
| 35 |
|
| 36 |
2) setup an http server giving access to "packages" and declare it as |
| 37 |
PORTAGE_BINHOST in make.conf at the client(s): |
| 38 |
|
| 39 |
== |
| 40 |
PORTAGE_BINHOST="http://example.com/packages/" |
| 41 |
EMERGE_DEFAULT_OPTS="-g" |
| 42 |
== |
| 43 |
|
| 44 |
The second line tells emerge to use binary packages by default and |
| 45 |
fallback to compilation if the requested pkg is N/A. This line should be |
| 46 |
used in both cases. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
HTH |
| 51 |
|
| 52 |
-- |
| 53 |
Best regards, |
| 54 |
Daniel |
| 55 |
-- |
| 56 |
gentoo-user@l.g.o mailing list |
Archives