[darcs-devel] Re: [PATCH] cvs2darcs wrapper script and GNU-ification

Steven G. Johnson stevenj at alum.mit.edu
Fri Nov 12 09:56:53 PST 2004


If anyone wants to try it out without applying the patches, running 
autoconf, etcetera, you can grab a tarball from:

	http://www.fftw.org/~stevenj/cvs2darcs-0.5.tar.gz

Note that I added a man page since yesterday, which is included in the 
above tarball (updated patch available upon request).

Untar it, run ./configure, and then you can run ./cvs2darcs directly 
from the source directory or you can 'make install' it.

Ganesh Sittampalam wrote:
> I promised a while ago I would find time to integrate and test various
> things people have sent me for cvs2darcs, and I haven't yet found time
> (was working on a big project, and am now in the middle of house/job move
> at the moment). If anyone else would like to step up to be the 'official'
> maintainer and host a repo etc I would gladly concede priority. Otherwise
> I will make an effort to look at this in the next month or so, but no
> promises.

I don't think I can be the sole maintainer, but I could help out a bit 
(at least maintaining my end of the scripts) if you wanted to add my 
public key to the http://abridgegame.org/repos/cvs2darcs repo.  Or is 
that controlled by David?

Note that the only change I made to your Perl scripts was to remove the 
--cvs-direct flag from branch-detect.pl, since it caused problems with 
one of my CVS projects and doesn't affect the semantics.  So, my 
additions are pretty orthogonal.

>>PS. My cvs2darcs script also supports importing branches if you pass -b
>><branch> -- it should automatically follow the chain of parents as
>>described in the README.  However, I haven't really tested this well
>>because I don't have CVS repositories with branches on my machine. 
> 
> For what it's worth, correctly handling branches is very important to me,
> and the main reason I started hacking on this.

I'd be much obliged if you (or someone else who has branches they care 
about) could try cvs2darcs -b <branch> <cvsmodule> from the above 
tarball and confirm that it works.

Hopefully, branch import should be a lot simpler now that the script 
automatically parses the branch_detect.pl output and follows the chain 
of parents for you.

Cordially,
Steven G. Johnson





More information about the darcs-devel mailing list