Paul Moore wrote:
>I've just started to use Subversion to manage source code, and overall
>I like the feel of it. However, a significant portion of my job is
>managing configuration files (Apache httpd.conf, Oracle init.ora,
>etc). I'd like to keep these files under some form of version control,
>as well.
>
>
This has been discussed rather recently on this list. My approach would
be to copy all the files you want under version control to a separate
location but with the same directory structure. Import that directory
into Subversion, then check out the repository to its "real" location.
From that point forward, all you have to do is "svn add" new
files/directories, as long as their parent directory is recognized as a
working copy.
For example, I have my entire /etc directory under version control,
although most files in there aren't versioned (which svn silently
ignores). Whenever I make a change to one of them, I just "svn ci" from
/etc and I'm good to go.
The only downside is having .svn directories in your "live" directories,
but that isn't a problem for me. If it is for you, you will indeed need
to keep them in a separate location and "svn export" to copy them over.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 21 22:49:23 2004