What are the condition on wc and repository?

[Peter Johansson]

When starting a run wc and repo must be in synch. If that is not fulfilled, an error msg is blurped. But what happens if something changes during the run? Someone could change the working copy or worse what if someone commit something to the repo. The latter is the interesting case because it is out of control of the user of svndigest. Does svndigest

1. Finish the work and different files may have output from different revs.
2. Some out of the range problem occur and depending what the memory picture svndigest crash or not.
3. Exit with an understandable error message.
4. Finish the work and committed revs after the start of run are ignored.

When in --enable-debug is set the run may be caught by an assertion. If 4) is not already the case it should probably be implemented by getting the HEAD rev number ar tart, save it, and use it when needed e.g. in SVNlog class. Note, if this is an issue , the severity grows when runtime grows.

[Jari Häkkinen]

For this we need a large enough repository to test on. BASE has a large repository but we do not want to make phony commits. We chould synchronize tests with some of the BASE developers regular commits.

[Peter Johansson]

How long time is a run on BASE project? If it is not long enough an easy way to slow it down is to slow down the repository access. I can do that from here on my slow line connection. Ho wlong is the parsing phase when running on lev?

[Jari Häkkinen]

(In [318]) Fixes #167 and addresses #74. Interfaces have changed. SVN::instance usage has changed, read SVN class documentation.