Date: Thu, 12 Jun 2003 19:17:10 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: jdp@polstra.com Subject: Re: The recent thread... handling new releases Message-ID: <p05210623bb0eb78017db@[128.113.24.47]> In-Reply-To: <20030612211821.GQ21995@electra.cse.Buffalo.EDU> References: <20030612180244.GG21995@electra.cse.Buffalo.EDU> <p05210620bb0e7675d934@[128.113.24.47]> <20030612211821.GQ21995@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
At 5:18 PM -0400 6/12/03, Ken Smith wrote: >On Thu, Jun 12, 2003, Garance A Drosihn wrote: > >> I have wondered if cvsup could be smart enough to download files >> under one name, and then afterwards (on a later run) know to just > > rename that file to the official name for a public release. > >... I have learned that the transfer mechanisms in use amongst >the mirrors varies widely, not all use cvsup. As far as I can >tell there is nothing that could do this in rsync for example, >I already know a bit more about rsync than cvsup. You just need some automatic way to do it for any transfer mechanism. Eg, 1) rsync (or otherwise copy) some small directory which has the meta-info on moving files around. 2) locally process the information found in that directory. 3) rsync (or otherwise copy) the larger repositories. (the above is easy for any "pull" strategy, at least. Doing it via a "push" strategy might take a bit more thought) I just mentioned cvsup because that's what I'm using, so I want this to all happen automagically with the cvsup-mirror port. :-) -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05210623bb0eb78017db>