Re: Caching CVSUP

For future reference, this question would have been more appropriate on 
-ports, but no worries.

Dave Horsfall wrote:

> I can't simply NFS-mount /usr/ports because of the differing releases

Why not? I have a setup similar to what you describe, with a lot more 
different releases hanging off of it as nfs clients. If you adopt the habit 
of doing 'make clean; make install clean' whenever you install a port, 
you've nothing to worry about. Or, if you prefer to leave things laying 
about in your ports tree on the server, use the WRKDIRPREFIX variable on the 
laptop.

The other alternative, as was already described, is to run a cvsup server on 
the server box. I actually do that too, since IME it's faster to cvsup the 
ports tree, even on the same machine, and with cvsupd running on the file 
server machine I can sync my laptop ports and cvs repo mirrors, as well as 
other stuff on my workstations, without having to do triple duty on the 
freebsd cvsup mirrors.

> likewise I can't quite see how [union]mounting /usr/ports/distfiles could 
> help, either.

Well, the obvious way it would help is that if you've already downloaded the 
distfile for a port once, you won't have to do it again? Although I'd skip 
making that directory a special case and just nfs mount the whole /usr/ports 
directory.

hth,

Doug


-- 

     This .signature sanitized for your protection

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"