Date: Tue, 9 Sep 2008 13:43:15 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 Message-ID: <20080909134315.375256b1@gumby.homeunix.com.> In-Reply-To: <BAY126-DS74F746C0A900C9F04109CCA550@phx.gbl> References: <51d7a5160809081441h6f952906ibea9d236a9c271dd@mail.gmail.com> <BAY126-DS7CC8BE7FC868CC542691DCA550@phx.gbl> <8d23ec860809081519l2bfb73fax8c82824c17a382bc@mail.gmail.com> <51d7a5160809081625o2856d25erf61e3c409c93ca9c@mail.gmail.com> <BAY126-DS74F746C0A900C9F04109CCA550@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Sep 2008 19:43:14 -0400 "Sean Cavanaugh" <millenia2000@hotmail.com> wrote: > I've never fully trusted portsnap. I do run portsnap fetch before > every portupgrade but I always follow it up with CVSUP and I usually > find some more files that get changed anyway. "portsnap fetch" doesn't affect your ports tree at all, you need to follow it with "portsnap update". There's no sense in in routinely mixing the two tools on the same tree. If you do find that portsnap isn't updating the tree correctly then you've either found a bug or have some corrupt data somewhere.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080909134315.375256b1>