Tailor http://nautilus.homeip.net/~lele/projects/tailor/ allows syncing between multiple source code control systems, and since there's several projects in unpleasant sccs's i thought I'd try converting them to darcs

• orange

orange certainly looks promising other than the fact they have bugs, don't have doc strings, and lack unit tests. though their tutorials were pretty straightforward.

Unfortunately they're a bunch of OSS windows developers, so their code is sitting in CVS (blech) so I wanted to convert out of it

My first attempts with earlier versions of tailor didn't work so I upgraded to the latest version, and it had problems as well.

What I ended up doing was checking the HEAD out of cvs first, and then telling tailor to convert it to a darcs repo, I don't know if this'll work when they commit something, but it's worth trying.

I used the following to start creating the config file.

$ tailor --verbose -s cvs -R :pserver:cvs@estelle.fri.uni-lj.si:/CVS --module orange -r INITIAL --subdir orange orange > orange.tailor

the file ended up like this

[DEFAULT] verbose = True

[py] target = darcs:targetpy start-revision = HEAD root-directory = /home/diane/src/orange state-file = orange.state source = cvs:sourcepy subdir = orange.cvs

[darcs:targetpy]

[cvs:sourcepy] module = orange repository = :pserver:cvs@estelle.fri.uni-lj.si:/CVS

[csrc] target = darcs:targetc start-revision = HEAD root-directory = /home/diane/src/orange/orange.cvs state-file = orange.state source = cvs:sourcec subdir = source

[darcs:targetc]

[cvs:sourcec] module = source repository = :pserver:cvs@estelle.fri.uni-lj.si:/CVS

• compclust

both chris and I want to try using darcs with compclust but that'll require 2way syncing.

http://www.darcs.net/pipermail/darcs-users/2005-January/005070.html