Paul Kirchner wrote:
Toby Johnson <toby <at> etjohnson.us> writes:
Dirk wrote:
For example we could accept a "directory map" input file such as:
${ROOT} = /trunk
${LABELS} = /labels
${ORPHANS} = /orphan
/projects/Website1 = /trunk/web/site1
/projects/Website2 = /trunk/web/site2
...
fly. But I would still stick to do the first 3 (ROOT, LABELS; ORPHANS)
during the conversion, and only to do some logical rearrangements
after the ActionHandler.
Yes, that's what I had in mind. The "correct" path would be used for all
internal use, such as renames and branches, and the path is only
converted at the very end after the other determinations have been made.
So it's really more of an operation on the dumpfile itself, than on the
actual VSS paths.
toby
In the example, the project paths are mapped with the VSS (pre-conversion) path
as the key. If the VSS path is the key, then it isn't possible to map labels.
Would it be possible use the post-conversion path, that is the paths after the
the ROOT, LABELS, and ORPHANS path mappings have been applied, as the key? For
example,
/trunk/projects/Website1 = /WebSite1/trunk
/labels/2.0/projects/Website1 = /WebSite1/tags/2.0
/trunk/projects/Website1Branches/Beta = /WebSite1/branches/Beta
This would allow labels to be mapped too, which would be useful.
I was planning on treating the labels and orphans directories as a
special case, in which case the two use cases are pretty much identical.
_______________________________________________
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
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
