Will creating a new folder break subversion?

Question

I have a subversion repository, but there are some things that I don't want it to mess with. For example, SVN breaks mac resource files because unix doesn't know about the resource fork.

However, I still want some form of back-up/version control. I would like to be able to just create a folder within the top level repository folder, and stick my stuff there. However, the readme.txt file in that folder says "don't touch this unless you know what you're doing".

So, is it safe to do that?

thanks.

Answer 1

You never ever should mess around with the repository folder directly.

Use an svn client and access the repository either via the file:/// url or set up a server (svn, apache) and then access the repository via svn:// or http(s)://.

And then you can create subfolders without any problems.

But I strongly recommend you read the Subversion book first (available free online), since you seem lack some basic knowledge about repositories and how to properly use Subversion.

Answer 2

Short answer, no. I'm assuming that you want to have a backup folder that you just store under the svn repository path (file heirarchy). I just tried it, it works fine. Of course, it doesn't include the files in a svn manner -- just old fashioned file heirarchy. This works if you want to save things like manual backups, or if your svn repo directory is actually on a RAIDed drive, for example.

Answer 3

To add to Stefan's answer: Make sure you understand the difference between the repository location (which holds the database and configuration for that repository) and the virtual folder structure that Subversion presents to users.

Answer 4

I'd be incredibly nervous about doing this.

Whilst it may not actively break subversion immediately, subversion is going to assume that it has complete control of all the folders within the repository, and that it knows what they all are. If some tool, script or process performs some generic action across all the files, you could find your backups mangled and/or the repository corrupted.

And just because it doesn't break it in the current version, doesn't mean that it won't cause problems in the next. So basically - I'd really avoid doing this, it's makes everything really messy.