Re: comparing cvsup vs. rsync

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

Dmitri Nikulin wrote:
> >     We could just distribute the CVS tree and write a front-end utility
> >     in csh or sh that we distribute along with the rest of the system
> >     to do the nitty gritty work of actually checking something out into
> >     /usr/src.  In fact, I think that would be preferable.
> NetBSD is distributed on pure CVS, anything else is a convenience.
> However, because CVS is so impressively bad for initial checkouts,
> they recommend downloading the rather small source and pkgsrc
> tarballs, and only using CVS for actual updates. This could work for
> DragonFly too, with the added bonus of pre-distributed cvs dotfiles or
> shell aliases. Maybe 'make update' (or whatever it is) could be wired
> to work that way too.

CVS is a beat concerning performance and CPU load, both for server and client.  I'd say rsync is the best deal for now.  cvsync does cvs-only (so, like rsync), but it has a bug which breaks the RCS files in some cases.  The author didn't want to fix it though :/  cvsync with checkout mode and the bug fixed would be definitely better than rsync.  Maybe we could do that on a weekend sprint, it doesn't seem too complicated to me.

cheers
 simon

--
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \

Attachment: signature.asc
Description: OpenPGP digital signature