On Fri, 18 Jan 2008 11:17:32 +0100 (CET) Helmut Jarausch <[EMAIL PROTECTED]> wrote:
> Hi, > > I haven't found out how to teach emerge to rsync > /usr/portage/packages > as well. > Both, /etc/rsyncd.conf on the server and > /etc/portage/rsync_excludes > > only exclude distfiles. > > There is no server problem, since an > rsync on the command line does fetch > packages, too > > Many thanks for a hint, > > Helmut Jarausch > > Lehrstuhl fuer Numerische Mathematik > RWTH - Aachen University > D 52056 Aachen, Germany For sure "emerge --sync" calls rsync with "--exclude packages" and I don't know a "legal" way to change this behaviour. If all you want is just to compile on one system and distribute the compiled packages elsewhere through the network, there are two methods that worked here with no problems: 1) export "packages" via nfs 2) setup an http server giving access to "packages" and declare it as PORTAGE_BINHOST in make.conf at the client(s): == PORTAGE_BINHOST="http://example.com/packages/"; EMERGE_DEFAULT_OPTS="-g" == The second line tells emerge to use binary packages by default and fallback to compilation if the requested pkg is N/A. This line should be used in both cases. HTH -- Best regards, Daniel -- [email protected] mailing list
