On 3/7/14, 8:24 AM, jrm wrote: >> Do not do anything in the .svn directory. That directory is >> exclusively for the use of the SVN working copy library and you could >> easily break your WC. > > Sure - if I overwrote something that has a genuine purpose - or created > something in a location where SVN expects exactly certain files to be. > But is SVN so fragile that it can't tolerate a differently named > subdirectory > or file under there? > > Or has experience taught you to treat SVN as fragile?
The proper solution is to use your own directory alongside .svn. Could you put it under .svn, it's likely you could do it and it would work. I wouldn't use tmp because while Subversion should be pretty tolerant to this there's no guarantee we won't make changes that would make it less so in the future. While we may take reasonable steps to avoid problems, we also have a completely reasonable belief that everything under .svn is for the exclusive use of Subversion and should only be modified using the methods that we use. For example. It's perfectly reasonable for us to take out an exclusive lock on the wc, look at the files in tmp, generate a new name based on that and then assume that some other program hasn't also decided to use that same name because we have an exclusive lock.
