On Thu, Feb 15, 2007 at 05:33:59PM +0100, Niclas Zeising wrote, and it was proclaimed: > On 2/15/07, Coleman Kane <[EMAIL PROTECTED]> wrote: > >On 2/15/07, Alexander Leidinger <[EMAIL PROTECTED]> wrote: > >> > >> Quoting Olivier Warin <[EMAIL PROTECTED]> (from Wed, 14 Feb 2007 > >> 19:54:09 +0100): > >> > >> > This issue is not only related to portupgrade, pkg_add a new port takes > >> > far too long now... and make index each time I upgrade my ports is > >> > awfull too. > >> > >> Regarding "make index": try "make fetchindex" right after the cvsup. > >> IT may not be up to the point with the cvsupped stuff, but not far off. > >> > >> Bye, > >> Alexander. > > > > > > > >I don't think we who use the modular X.org tree can do this since a number > >of the ports won't be properly registered in the file (or am I off-base > >here?). > >-- > >Coleman > > We who use the modular xorg tree cant do make fetchindex, we have to > do make index... I've never had any problem with portupgrade taking > forever to run if i've done a make index and a portsdb -u before > running. But then again, I only have somewhere around 350 ports at the > moment. > > //Niclas
I have over 1000 ports installed and it can be annoyingly slow. I don't completely know if the "portupgrade" script is the 100% culprit though, as it calls a number of other programs during execution. -- coleman _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
