I have a subversion repository on a network shared folder. It is not a subversion server, just a disk that multiple computers can read and write to.
Different computers map network drives in different ways. How do I make it so that if svn can't find the folder on one path it automatically tries another?
Or more generally, how can you specify a list of locations to commit to?
Unfortunately, this isn't something that's easy to do. File systems aren't set up for it, and most applications desire a hard failure when something's missing. Subversion is really designed to have a single, master place that it commits to.
It really sounds like you either need to run an always-available SVN server, or switch to a different version control system. The former is the standard use case, and what most subversion tools are set up for.
It's slightly unclear what you're doing, but another alternative might be to set up a post-commit hook (again you'd need a server to do this) that would update, export, or check out the repo to various points on your network whenever a commit happens.
If you were willing to look at alternatives, Git and Mercurial are the two big distributed version control systems which are probably better suited to your needs.
On Windows SVN is able to check out files from a remote server. Say your file server is fileserver , your share is files and the path is foo\bar\baz (You can type net use in a cmd window to show the server/share mappings of your network drives). So your repository is \\fileserver\files\foo\bar\baz. Then you check out a working copy from the server path file://fileserver/files/foo/bar/baz.