On Wed, Mar 21, 2007 at 10:59:22AM +0100, Stefan Sperling wrote: > On Wed, Mar 21, 2007 at 01:39:51AM -0700, Kernel Monkey wrote: > > I've been using the cvsup client to update my sources. What is the > > difference between cvs and cvsup when updating sources? > > > > Is one better than the other? > > There is no easy answer. > It depends on what you want. > > + cvsup is much faster. It's optimized for getting as much > out of your bandwidth as it can. > See http://www.cvsup.org/howsofast.html > + cvsup can copy the whole OpenBSD CVS repository, not just > check out working copies. You can even add local branches to > the repo and commit on them! See the development(7) man page > from FreeBSD for a nice guide written by Matthew Dillon himself > on how to do this. > - cvsup does not provide encryption > - cvsup only works on i386 > + cvsup is written in modula3 (yes, this is a +, but just > because I am familiar with the cm3 compiler from work, > ie. the existence of modula3 and killer apps that use it > have been paying some of my rent. Keep them coming! :-P) > > - cvs is slower > + cvs can do diffs and view logs, and using the nifty cvsdo utility > from the cvsutils port you can even diff new files you've added > + cvs provides encryption over ssh > - but many anoncvs mirrors probably sync using sup/cvsup, so the > encrypted distribution channel provided by anoncvs does not go all > the way up to the master server anyway... :-( This may or may not > cancel out the benefit of encryption for you. > + cvs works on all arches
Great points but one to add: *cvs is part of base, cvsup is yet another port/package I have to install and maintain. > > -- > stefan > http://stsp.in-berlin.de PGP Key: 0xF59D25F0
