> Thanks for your reply and sorry for the typo. Yes cache-init also took > > a couple of hours on my computer, but when it finished i got the > > command-promt > > back. But I am having problems with cache-update. I include the last > > paragraphs of my original post with the typo corrected: > > > > for upating the portstree I do: > > # cvsup -g -L 2 ports-supfile > > # cache-update > > # portindex -o /usr/ports/INDEX-5 (I am using 5-stable) > > # portsdb -u (I am also using portupgrade) > > # portupgrade -arR (or whatever) > > What happens if you add > > # make fetchindex > > immediately after the cvsup?
I just tried it and it does not change the behaviour of cache-update. cache-update still shows a short burst of activity before it becomes idle, but does not return to the command promt. But if I understand it correctly, isn't the whole purpose of the portindex-suite to provide yet another mechamism to create an up to date INDEX(-5) file, but both being faster than 'make index' (portsdb -U) and more up to date than 'make fetchindex'? So wouldn't the 'make fetchindex' kind of defeat the purpose of using portindex? Sorry, for all the questions, I am still trying to figure this all this out for myself. I am still quite unexperienced in FreeBSD .. ;-) Christopher _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
