Keeping up to Date Repository Shadows

I'm sure this issue has come up before, but after searching, I didn't find a clear solution to it. Some revision control tools, such as Microsoft Visual Source Safe, provide a shadow directory that is an exact copy of all projects and files that your repository contains. Obviously, this feature doesn't exist by default in Subversion. I started trying to work around this and create my own.
 
First, I tried making wrapper scripts around the subversion commands, and updating a second working copy upon all related subversion commands. This didn't work so well, and the maintenance was rough.
 
I then found out about hook scripts and tried to implement one of those in start-commit and post-commit, but had little success. Is there documentation on what environment variables/parameters are passed into the hook scripts?

I also tried looking at the svn export command, but realized that it doesn't meet my needs, as it would be highly inefficient to rewrite the whole shadow on a project or folder level if little changed on a commit.

So, does anyone have an easy way of implementing shadow directories in subversion? Thanks so much for any help you can provide.

                        
---------------------------------
Do you Yahoo!?
 Check out the new Yahoo! Front Page. www.yahoo.com/a
Received on Thu Nov 4 17:43:06 2004