Date: Thu, 18 Oct 2001 23:46:53 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: jason andrade <jason@dstc.edu.au> Cc: hubs@FreeBSD.ORG Subject: cvsup, FreeBSD-CVS tree and branches Message-ID: <200110190346.f9J3krv72021@khavrinen.lcs.mit.edu> In-Reply-To: <Pine.OSF.4.20.0110191232140.29121-100000@azure.dstc.edu.au> References: <Pine.OSF.4.20.0110191232140.29121-100000@azure.dstc.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 19 Oct 2001 12:36:08 +1000 (EST), jason andrade <jason@dstc.edu.au> said: > Quick query for the cvsup (and non cvsup?) mirrors out there. > Where do you put your cvsup tree that is used to serve end users ? /u/cvsup, but that's an implementation detal. > is /pub/FreeBSD/development/FreeBSD-CVS/ > on ftp.freebsd.org, the root of the various cvsup trees ? > or is it a checked out full version of the cvsup tree, but not > actually suitable to seed a cvsup(d) tree ? No. > i'm trying to figure out where the files should live in the > context of minimizing downloading the same data multiple times. On my system, I exclude (on the rsync client side) all of the unpacked source code bits; specifically: /development/FreeBSD-CVS /branches/-current/www /branches/-current/doc /branches/-current/ports /branches/2.2-stable/ports /branches/3.0-stable/ports /branches/4.0-stable/ports /branches/-current/src /branches/2.2-stable/src /branches/3.0-stable/src /branches/4.0-stable/src /branches/-current/sup /branches/2.2-stable/sup /branches/3.0-stable/sup /branches/4.0-stable/sup /branches/-current/supfile.cvsup /branches/2.2-stable/supfile.cvsup /branches/3.0-stable/supfile.cvsup /branches/4.0-stable/supfile.cvsup /doc/mailing-lists/archive /doc/mailing-lists/supfile.cvsup /doc/mailing-lists/sup The presence and contents of the `supfile.cvsup' files and `sup' directories on ftp-master should be a big clue to you as to how they are maintained. I personally update the 2.2 tree once a week, and all of the other trees every six hours (in the same cron job as runs the rsync itself). I don't provide the CVS tree itself in FTP space; there are far better mechanisms for that now, although since I'm no longer in a disk-space crunch I might well add it back. > in config-speak, does the following make sense ? > cvs-all release=cvs prefix=/pub/FreeBSD/development/FreeBSD-CVS > src-all prefix=/pub/FreeBSD/development/FreeBSD-CVS > ports-all prefix=/pub/FreeBSD/development/FreeBSD-CVS No. You should use the collection of configurations provided to you by the project. In particular, you do not even come close to replicating the complete set of cvsup collections. Your supfile should look like this (taken from the cvsup-mirror port): cvs-all release=cvs prefix=prefixes/FreeBSD.cvs gnats release=current prefix=prefixes/FreeBSD-gnats.current www release=current prefix=prefixes/FreeBSD-www.current mail-archive release=current prefix=prefixes/FreeBSD-mail.current distrib release=self prefix=prefixes/distrib.self `prefixes/distrib.self' should be a symbolic link pointing to the parent directory of the `sup' directory in which cvsupd's control files. If you need an account on a mirror to see how all of this works, please contact me privately. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110190346.f9J3krv72021>