/usr/portsnap vs. /var/db/portsnap
Colin Percival
cperciva at freebsd.org
Sun Aug 7 13:04:45 GMT 2005
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
More information about the freebsd-arch
mailing list