"Jens B. Jorgensen" <jens.jorgensen@tallan.com> writes:
> Ok, so I've gotten started writing vss2svn.py, a utility to do a
> one-time conversion from Visual SourceSafe to svn. Naturally this is a
> personal itch I'm scratching since I'd like to get my current client
> to switch over. I've been going over cvs2svn.py and I'm following the
> same basic approach: I'm using the vss automation interface to iterate
> over the repository tree and generating a flat file with timestamp,
> author/comment hash, rev #, and path and then sorting that file and
> processing it line-by-line to generate a dump file. At least at this
> stage (because it suits my own needs) I'm completely ignoring the
> "branch" and "share" "features" of VSS since we have not (and would
> not!) ever use them. All we have then are adds, commits, renaming, and
> deletions (haven't decided what to do about labeling but since we
> don't use it in the obvious tag-like way I'm thinking of taking the
> cowards way out on that one). My first thought was naturally to re-use
> as much of cvs2svn.py as possible. On the other hand cvs2svn.py does a
> lot of things that are necessary to handle cvs but are not
> needed/necessary for the simple cases I'm dealing with and
> disentangling what vss2svn.py needs from cvs2svn.py (especially when
> it is under such active development, cvs2svn.py has a median time
> between checkins of 23.94 hours!) could prove to be a lot of work and
> perhaps more than I can devote.
If you can get the VSS data into the format of the
cvs2svn-data.revs
file, then cvs2svn.py can finish the job for you. (Of course, the RCS
checkout will have to be some other command, but that's trivial.) To
do this, you probably need to replace CollectData and the rcsparse
stage with something else, that's all.
I don't know if this is a reasonable format for VSS's semantics, just
pointing it out. Based on what you said, though:
> There seems to be
> enough in common between these two (the kind off VSS functionality I'm
> doing seems like a strict subset of the cvs functionality) that there
...I'm guessing it is reasonable.
> Another thing I guess I'm wondering is if anyone else out there has
> already written what I'm writting and I'm wasting my
> time. Alternatively perhaps there are those out there that would like
> to use such a beast and would have an immediate need. We could join
> forces and if nothing else perhaps others could use and test the stuff
> I'm writing.
Check out clkao's work on a Subversion VCP destination driver at
http://public.perforce.com/public/revml/index.html
http://svn.clkao.org/revml/
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 16 18:59:11 2003