Dirk wrote:
Hello Toby,
I'm working on my label handling and had some good progress. I'm now
stuck with a situation where a file item carries the same label as one
of the parent projects. The reason for this is, that you can label the
parent and later move the label on one of the files explicitly. In
order to track this and to fallback into a commit action, I need to
know the state of the current repository. This is exactly what you did
in your sanity checker, except, that it does not handled recursive
copying, that is, if you copy a directory, only the directory is
copied and not the childs. This is actually a similiar issue like the
delete project issue
Additionally I need to call the sanity checker from within the
_label_handler without the complete error handling.
Therefor I though about the following: would it be possible, that we
move the SanityChecker into a seperate module. It should have a query
interface, like "Does itempath exists/not exist", and a kind of replay
interface, to perform the actions of the nodes onto the current state.
Then we both could use the sanityChecker for querying, what should
happen, and finally we would apply all nodes to the checker, when we
dump them into the dumpfile. In this case the captured hierarchy would
be identical to the state of the repository. I just fear, that we also
must take care of the complete revision mapping, since in a recover
case, we must know the state of the repository at that time.
Hi Dirk, sorry again for the delay in replying, but it looks like in the
meantime you have implemented the change you suggested. Sounds like a
good idea, and the way you implemented it looks fine to me.
I am working on a couple of the outstanding 0.10 tickets now and hope to
get a "release candidate" for it released soon. At that point I think it
would be a good idea to move 0.10 development to a branch, and merge
your pin_handler branch to the trunk, since it will be the basis of the
next release. Sound like a good plan?
toby
_______________________________________________
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
