Bear in mind, though, that you can easily do a simple SVN command to move the directories of the newly created small repository as desired after the fact. The beauty of Subversion is that you can do that move and all the history and logs of the files within will be maintained.

However, if you plan on automatically running this script on a regular basis, this manual solution obviously won’t help you. So, the only solution I can see is to write code that will check out the new small repository, then loop through the directory’s contents and do a SVN MOVE command on each item in the directory. This will be some work to set up, but it will then be completely automated, and will enable you to get rid of the irritating duplicate directory at the root level.

Sorry, no graceful solution for you that I can see. Of course, the other option is to just live with the duplicate directory.

Thanks for sharing the code – very, very useful indeed

However, I am having two problems to get it to work for me:

1. The new repositories maintain reference to the folder in the original repository and this end up duplicated in the new path stucture – e.g.: to checkout the new smaller repository contents I now have to ‘svn co svn://server/new_smaller_rep/new_smaller_rep‘

2. I am having authorization errors on commit – I upgraded from 1.4.6 to 1.5.4.

Any suggestions on how to solve these issues? (I reckon this is only one issue – the first one – but any help would be gladly appreciated)

Cheers,
Nelson