From owner-freebsd-questions@FreeBSD.ORG Wed May 14 00:18:17 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46757106567B for ; Wed, 14 May 2008 00:18:17 +0000 (UTC) (envelope-from fbsd06+V5=63d7240c@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id 193F68FC1C for ; Wed, 14 May 2008 00:18:17 +0000 (UTC) (envelope-from fbsd06+V5=63d7240c@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by turtle-in.mxes.net (Postfix) with ESMTP id 0730E16464C for ; Tue, 13 May 2008 20:06:17 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 67BB323E408 for ; Tue, 13 May 2008 20:06:14 -0400 (EDT) Date: Wed, 14 May 2008 01:06:12 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080514010612.28dc78ce@gumby.homeunix.com.> In-Reply-To: <6e5cf6a70805131027i3f7286d0jadacbab8f862b101@mail.gmail.com> References: <6e5cf6a70805131027i3f7286d0jadacbab8f862b101@mail.gmail.com> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: rsync'able ports tree instead of csup? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 00:18:17 -0000 On Tue, 13 May 2008 13:27:05 -0400 "Joachim Rosenfeld" wrote: > My usual workflow with the ports tree (and to a lesser > extent, /usr/src) goes something like this: > > 1. download ports/src tree from cdrom/ftp site (usually done once) > > 2. use csup to update to HEAD > > 3. build As I understand it, it's advisable do an initial csup to the exact version in the snapshot, before doing the csup to the latest version. If you skip this then csup wont delete files removed between the snapshot and the current tree. If you are unlucky that could lead to persistent problems that are hard to diagnose.