Date: Mon, 20 Dec 2004 10:56:21 -0600 From: Joshua Lokken <joshua.lokken@gmail.com> To: Joshua Tinnin <krinklyfig@spymac.com> Cc: freebsd-questions@freebsd.org Subject: Re: (cvsup newbie questions) Message-ID: <bc5b63850412200856701e69b1@mail.gmail.com> In-Reply-To: <200412200813.06057.krinklyfig@spymac.com> References: <003b01c4e489$6497d0e0$9a11a8c0@d3stomc> <41C4F0CC.30700@nbritton.org> <bc5b638504122006084f4ea297@mail.gmail.com> <200412200813.06057.krinklyfig@spymac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 20 Dec 2004 08:13:05 -0800, Joshua Tinnin <krinklyfig@spymac.com> > IIRC, pkgtools.conf only works with the pkgtools apps, like portupgrade. > I don't think it works with making the port from the tree itself (like > if you cd to the folder and make install clean), but options you use in > building it from the ports tree will be stored > in /var/db/ports/<portname>/options, as mentioned above. This is what I > meant by "remembered." Yes, correct. > > > Also, semi related, whats this "Generating INDEX-5 - please wait.." > > > thing and why does it take an hour for it to generate? > > > > The machine is building the ports collection INDEX-5 file from the > > make describe output of all of the ports. You can simplify this > > process by doing 'make fetchindex' after you cvsup each time. > > Yes, although you should cd /usr/ports before you do that. I guess the > way people are doing this now is cvsup ports, cd /usr/ports && make > fetchindex && portsdb -u (this last step will be done automatically > when it needs to be done, but you can do it anyway after a ports tree > update). You can also use /usr/ports/sysutils/p5-FreeBSD-Portindex , > which speeds up the process of making a new INDEX locally. Ah, yes, it does help to be in /usr/ports when one runs 'make fetchindex'. -- Joshua Lokken Open Source Advocate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bc5b63850412200856701e69b1>