Hi Mike,
you probably have followed this mailinglist a little. The next major
step in the vss2svn converter is to directly decode the binary archive
files. But we have not yet released an official version. So we consider
the current state as ready for beta. But with a 9 year old archive, I
would expect you will see a few pitfalls.
ssphys is only the backend doing the decoding of the binary files. All
higher logic is done in the perl converter vss2svn. So normally you
don't have to use ssphys directly. vss2svn takes care for it. But if you
want, you can play with "ssphys --help"
Since vss2svn creates the dumpfile by itself there is no need in knowing
the path to svn. Therefore there is also no configuration option for it.
Currently the converter can not perform the conversion on a single
subproject or limit the conversion to a specific time interval. But you
can use two methods to achieve this:
* Perform a full conversion, but use the svndumpfilter when importing
into a repository
* Make a local copy of you current VSS archive and recursively destroy
unsused projects
The second option reduces the size of the data that needs to be
converted and thereby reduces the time needed during the conversion.
This is also a "safe" option to minimize the amount for the conversion,
since the destroy action will only destroy information that is not
shared throughout your archive. (But be sure that you use this path on a
local copy of your archive)
I would suggest you start with the current nearly beta status and see,
whether you run into problems. If so, I would invite you to help fix bugs.
Dirk
I do need to exclude stuff from the conversion though, the 9 years of "code"
is enough. We don't need all the history of the other crap.
Everything we need is in one project, can ssphys work on a single project
path, and no other?
I'll happily modify the perl, if someone can tell me the argument format to
ssphys.**
Thanks
* The last, after 14000 commits, and over a week of processing, down to one
newly added passwordless user already existing with a password. My fault,
obviously.
** On the subject of arguments, am I mistaken or can you not change the path
to svn ($gCfg{svn}) on the command line? svn isn't listed in GetOptions.
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
