Date: Wed, 23 May 2012 10:34:52 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: freebsd@dreamchaser.org Cc: freebsd-questions@freebsd.org Subject: Re: portsnap update won't update original /usr/ports Message-ID: <4FBC37B4.7060908@ShaneWare.Biz> In-Reply-To: <4FBC1B06.6060102@dreamchaser.org> References: <4FBC1B06.6060102@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23/05/2012 08:32, Gary Aitken wrote: > According to the handbook, one can do portsnap fetch portsnap update > and the update will work with a previously created ports tree; I > presume this includes one created during system install. > > However, when I attempted this, portsnap complained: /usr/ports was > not created by portsnap. You must run 'portsnap extract' before > running 'portsnap update'. > > Is there a way to use portsnap against this tree, or must I delete > the existing /usr/ports and do an extract first? > 'portsnap extract' will write over whatever is in /usr/ports so you don't have to delete what is there. Any distfiles or packages will remain intact. You need to start with 'portsnap extract' so that portsnap gets a reference point to use for updates - which only adds changes since last update
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FBC37B4.7060908>