From owner-freebsd-ports@FreeBSD.ORG Fri Jan 30 12:06:21 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58AE016A4CE for ; Fri, 30 Jan 2004 12:06:21 -0800 (PST) Received: from lakemtao02.cox.net (lakemtao02.cox.net [68.1.17.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4336D43D2F for ; Fri, 30 Jan 2004 12:06:18 -0800 (PST) (envelope-from A.J.Caines@halplant.com) Received: from mail.halplant.com ([68.100.162.49]) by lakemtao02.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040130200618.KXVT19763.lakemtao02.cox.net@mail.halplant.com> for ; Fri, 30 Jan 2004 15:06:18 -0500 Received: by mail.halplant.com (Postfix, from userid 1001) id 76CE41A; Fri, 30 Jan 2004 15:06:17 -0500 (EST) Date: Fri, 30 Jan 2004 15:06:17 -0500 From: Andrew J Caines To: freebsd-ports@freebsd.org Message-ID: <20040130200617.GQ78925@hal9000.halplant.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <401910EA.8090102@updegrove.net> <40194920.7080003@updegrove.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40194920.7080003@updegrove.net> Organization: H.A.L. Plant X-PGP-Fingerprint: C59A 2F74 1139 9432 B457 0B61 DDF2 AA61 67C3 18A1 X-Powered-by: FreeBSD 4.9-STABLE X-URL: http://halplant.com:88/ X-Yahoo-Profile: AJ_Z0 X-ICQ: 283813972 Importance: Normal User-Agent: Mutt/1.5.5.1i Subject: Re: cvsup ports and portupgrade -rva . X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew J Caines List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 20:06:21 -0000 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 |