From owner-freebsd-questions@FreeBSD.ORG Mon Nov 26 13:15:49 2007 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 A04FE16A41B for ; Mon, 26 Nov 2007 13:15:49 +0000 (UTC) (envelope-from fbsd06+QT=f3b4e1e2@mlists.homeunix.com) Received: from mxout-04.mxes.net (mxout-04.mxes.net [216.86.168.179]) by mx1.freebsd.org (Postfix) with ESMTP id 78E8013C4CC for ; Mon, 26 Nov 2007 13:15:49 +0000 (UTC) (envelope-from fbsd06+QT=f3b4e1e2@mlists.homeunix.com) 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 24DF1D05A5 for ; Mon, 26 Nov 2007 08:15:47 -0500 (EST) Date: Mon, 26 Nov 2007 13:15:45 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20071126131545.5e52885b@gumby.homeunix.com.> In-Reply-To: <474A8CA5.60300@infracaninophile.co.uk> References: <20071121221955.10f80f09@tania.servebbs.org> <20071123032011.57dcfc96@gumby.homeunix.com.> <200711260452.lAQ4qVuN098618@banyan.cs.ait.ac.th> <20071126072727.GA3259@slackbox.xs4all.nl> <474A8CA5.60300@infracaninophile.co.uk> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Personalised patches in ports 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: Mon, 26 Nov 2007 13:15:49 -0000 On Mon, 26 Nov 2007 09:06:45 +0000 Matthew Seaman wrote: > 'portsnap extract' or 'portsnap update' will however blow away local > additions in the part of the ports tree it is operating on -- there > are clear warnings to that effect in the man page. There are clear warnings that 'portsnap extract' will delete extra files, but not for 'portsnap update'. And my recollection, from when I briefly tried portsnap, is that it leaves derived files, like README.html, untouched. So I guess that after the initial extract is done portsnap behaves like csup in this respect. I think the main difference between csup and 'portsnap update' is in the way they handle files that are under CVS, such as port makefiles. csup always removes changes, which I like because I know where I stand. I think with portsnap it depends on the CVS history.