Date: Fri, 30 Jan 2004 15:06:17 -0500 From: Andrew J Caines <A.J.Caines@halplant.com> To: freebsd-ports@freebsd.org Subject: Re: cvsup ports and portupgrade -rva . Message-ID: <20040130200617.GQ78925@hal9000.halplant.com> In-Reply-To: <40194920.7080003@updegrove.net> References: <401910EA.8090102@updegrove.net> <40194920.7080003@updegrove.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rick, > What is the preferred method to keep the installed ports and ports trees > synced between identical servers? If you explicitly want to keep ports trees on multiple systems in sync, then the canonical method is to use cvsup to update from the mirrors to a server, then use cvs to update the clients (including the "server"). On the other hand if you only want to keep the ports themselves in sync, then the two likely approaches are sharing the ports tree and distributing packages. Sharing the tree means that you can easily build and install for multiple architectures, or for a single architecture you can update and build on one system and install on many. I've not tried it, but I'd imaging that something like "portupgrade --noclean --nocleanup --all" would run nicely on the client systems. If you don't like sharing filesystems, you can build and package on one system (for each architecture), then distribute those packages to the other systems. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@halplant.com | | "They that can give up essential liberty to obtain a little temporary | | safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040130200617.GQ78925>