Date: Sat, 11 Oct 2003 14:25:23 -0700 From: Kent Stewart <kstewart@owt.com> To: jdroflet@canada.com Cc: freebsd-questions@freebsd.org Subject: Re: Why has cvsup moved ports to attic ? Message-ID: <200310111425.23601.kstewart@owt.com> In-Reply-To: <20031011132143.1712.h010.c009.wm@mail.canada.com.criticalpath.net> References: <20031011132143.1712.h010.c009.wm@mail.canada.com.criticalpath.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 11 October 2003 01:21 pm, jdroflet@canada.com wrote: > On Sat, 11 Oct 2003 10:58:30 -0700, Kent Stewart wrote: > > Message-Id: <200310111058.30135.kstewart@owt.com> > > From: Kent Stewart <kstewart@owt.com> > > <snip> > > > of ports-all. If you use portupgrade and its tools, you also have > > to rebuild INDEX.db. > > > > Kent > > Thanks for prompt solution Kent, > I had not built a machine over the summer so did not realize the > changes, to rebuild the INDEX is it merely a 'make index' in > /usr/ports ? > Yes, that does it. If you are redoing some of this, seriously consider portupgrade. It makes updating ports much easier. It doesn't change building and initially installing a port but the port system is continuously changing thing. You have to run "portsdb -u" to create the INDEX.db, which is used by the portupgrade tools. Some people use "portsdb -uU" to generate both but I still use "make index". FWIW, the current INDEX is 8-days old and INDEX-5 is over 7-weeks old. Bind9 was moved to ../dns five weeks ago. So, the change would be in one of the INDEXs and not the other. Once you start rebuilding the INDEX files, consider adding ports/ INDEX[-5] to your ports-all refuse file. It doesn't make sense to redownload them everytime you cvsup and then rebuild them. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310111425.23601.kstewart>