Re: cvsup in 1.4?

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

On 29.12.2005, at 20:54, Matthew Dillon wrote:
>     Excuse me a moment while I go off into a corner and scream bloody
>     murder at the authors of ezm3 (which cvsup needs to build).  There 
> are,
>     literally, HUNDREDS of os-dependant files, no worthwhile 
> documentation,
>     and no mechanisms that I can see to help port to a new OS or 
> generate
>     any of the required dependancies.  There are insane dependancies 
> that go
>     deep, deep into system internals.  If there is a poster boy on how 
> NOT
>     to write a language, ezm3 would be it :-(.

Heh, I said about the same when I tried porting it...

>     I am just going to take the cvsup binary from FreeBSD-4 and make 
> the
>     nrelease build use it directly.  Fortunately we still ship with 
> all the
>     required compatibility libraries.  Then we will shift away from 
> using
>     cvsup for 1.5 and later.  I really love the cvsup program, but the
>     language support is just too much of a headache.

Yes, that's what I wanted to discuss some time ago.  To sum up again:

Possibilities to sync a CVS tree:
- rsync: pretty standard, not optimized for CVS, but fairly optimized
- cvsync: in its current version cripples some RCS,v files

Possibilities to sync a checked out tree:
- rsync: needs a checked out tree on every mirror.  bad imo.
- csup: still needs a cvsupd running.
- anoncvs: eats lots of disk IO on the server

Or: write one ourselves.  Another project which basically is meta.

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: PGP.sig
Description: This is a digitally signed message part