Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Aug 2005 06:00:47 -0700
From:      Colin Percival <cperciva@freebsd.org>
To:        Kirill Ponomarew <krion@voodoo.oberon.net>
Cc:        Jeremy Messenger <mezz7@cox.net>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject:   Re: /usr/portsnap vs. /var/db/portsnap
Message-ID:  <42F605FF.7020403@freebsd.org>
In-Reply-To: <20050807125347.GA43837@voodoo.oberon.net>
References:  <42F47C0D.2020704@freebsd.org> <42F51979.2020509@FreeBSD.org> <42F54DD4.7080901@freebsd.org> <op.su4gzdps9aq2h7@mezz.mezzweb.com> <42F59AA8.2030605@freebsd.org> <20050807125347.GA43837@voodoo.oberon.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Kirill Ponomarew wrote:
> On Sat, Aug 06, 2005 at 10:22:48PM -0700, Colin Percival wrote:
>>Portsnap will not remove any ports which it doesn't know about.  Portsnap
>>will only remove local modifications when they are in a port or infrastructure
>>file (e.g., Mk/*) which portsnap is updating to a newer version.
> 
> Is portsnap also immune to Makefile.inc[local] and doesn't delete
> them during update ?

Portsnap only removes files or directories if they are in the way.
If ports/foo/bar doesn't exist in the ports tree, then portsnap will
not touch /usr/ports/foo/bar.  If ports/fizzle/baz exists in the
ports tree, then portsnap will delete /usr/ports/fizzle/baz the
next time that "portsnap extract" is executed (which shouldn't
happen very often, since that extracts a complete new ports tree)
or after the next time that ports/fizzle/baz is updated in the ports
tree.

Colin Percival



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42F605FF.7020403>