Date: Wed, 4 May 2005 17:13:59 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Jim Campbell <jim-c@charter.net> Cc: freebsd-ports@freebsd.org Subject: Re: Problem with portsdb Message-ID: <20050504171359.6583950f.wmoran@potentialtech.com> In-Reply-To: <4279312F.20207@charter.net> References: <4279312F.20207@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[Please keep the mailing list in the loop, primarily so this information gets archived so the the next person searching can find it.] Jim Campbell <jim-c@charter.net> wrote: > Wesley and Bill, > > You both suggested the same solution. Before I go off and do it, I need > to be clear about something. Having done a "make fetchindex" I should > NOT do a "make index" or "portsdb -uU" since that would overwrite the > just-fetched INDEX. Is this correct? That's correct. If you run "make index" it will overwrite what you just fetched, thus undoing the fetchindex. portsdb with -U will do the same as a "make index". It's OK to do a "portsdb -u", but this isn't required, as it will do this on demand anyway. If you've got an up-to-date version of portupgrade, it actually does the fetchindex for you when it notices things are out of date, but older versions automatically do "make index" ... so make sure your portupgrade is updated first. -- Bill Moran Potential Technologies http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050504171359.6583950f.wmoran>