Re: Modify files in start-commit

On second thought, how about this: don't change the transaction, but
keep the VERSION file in a separate repository, that you reference
through svn:external. That way, you don't modify the contents of the
transaction - you just add a second transaction. Of course it's your
responsibility to tie together these transactions. But if you first do
your normal pre-commit checks (if any), then commit the VERSION
transaction, and if that succeeds return a yes from the pre-commit hook,
then the chances of the overall transaction failing are small and the
consequences minimal.

-- 
Stein