Date: Sun, 27 Jan 2013 15:28:34 +0000 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: Cronjob Cvsup -> What? Message-ID: <20130127152834.1d7b8201@gumby.homeunix.com> In-Reply-To: <201301270951.13292.mrkvrg@acm.org> References: <20130127001805.97F0119B@hub.freebsd.org> <5104E6B7.9070302@aboutsupport.com> <5105057F.3090108@FreeBSD.org> <201301270951.13292.mrkvrg@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 27 Jan 2013 09:51:12 -0500 MFV wrote: > Hello Matthew, > > Thanks for an outstanding piece of documentation. It resolves a > number of concerns I had and convinced me to move from portsnap where > I discovered an apparent bug that gave me security concerns. More > specifically I manually edited /usr/ports/UPDATING and portsnap did > not recognise the change and download a proper copy. I don't see why that's a problem. The function of "portsnap update" is to update files in the tree that have been updated, deleted or added in the repository. Resynchronising the tree and it's metadata with the snapshot is what "portsnap extract" is for.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130127152834.1d7b8201>