Date: Tue, 22 May 2012 21:30:44 -0400 (EDT) From: Thomas Mueller <mueller23@insightbb.com> To: freebsd@dreamchaser.org Cc: freebsd-questions@freebsd.org Subject: Re: portsnap update won't update original /usr/ports Message-ID: <1800315639.3547775.1337736644930.JavaMail.root@md03.insight.synacor.com> In-Reply-To: <4FBC1B06.6060102@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: Gary Aitken <freebsd@dreamchaser.org> To: freebsd-questions@freebsd.org Sent: Tue, 22 May 2012 19:02:30 -0400 (EDT) Subject: portsnap update won't update original /usr/ports 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? Thanks, Gary ---- My response: ---- I screwed up this way too, when I downloaded the USB memstick image for FreeBSD 9.0_BETA1 and later, BETA2, I installed the ports from that, which worked to my disadvantage when I later ran "portsnap fetch update". I wound up deleting /usr/ports/* and starting fresh, may not necessarily have had to delete the ports tree. But now it works. Now I wonder if it's feasible to switch between "portsnap fetch update" and csup <ports-supfile>, or if it's strictly one or the other. I am at webmail interface, which strongly favors top-posting over bottom-posting; feel more comfortable with vi editor.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1800315639.3547775.1337736644930.JavaMail.root>