[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

vss2svn.py: underway and looking for suggestions/collaboration/...

From: Jens B. Jorgensen <jens.jorgensen_at_tallan.com>
Date: 2003-07-16 18:40:34 CEST

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

So I guess what I'm looking for from the community is perhaps guidance
(goadance?). It seems The Right Thing To Do is to least abstract out
class Dumper from cvs2svn.py (kfogel: care to jump in and comment?) and
put it in a separate module that both cvs2svn.py and vss2svn.py could
use. Or, maybe since the overall structure is very nice and probably
reusable perhaps go further and abstract out the whole structure of the
process and let the cvs-specific and vss-specific stuff be a sub-class
of some generalized class. 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 certainly seems to be
opportunity to leverage the work done in a more productive and valuable
way than just the classic reuse form (copy-n-paste).

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.

Anyone care to comment?

Jens B. Jorgensen
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:41:20 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.