[svk-users] svk and administration

[Pierce T. Wetter III]

  Ok, so I read this:

http://lists.debian.org/debian-devel/2005/02/msg00495.html


  Which is pretty cool and all. I want to store my system config  
files in version control, but I don't want to store everything in / 
etc, and I didn't want to have to have the .svn file around. I was  
thinking I was going to have to write some sort of script to use  
rsync and clone files out of /etc into a separate directory, and back  
again that would all sit on top of svn.

So this svk solution sounds cool. Importing all of /etc seems like  
overkill, I'm wondering if some svk expert could give me some tips on  
how to solve this problem more efficiently.

  My dream solution: (mds)

    1. Would take a file/directory on an arbitrary path and let me  
add it to version control.

       mds add /etc/httpd/
       mds add /etc/hostconfig

    2. Would then be able to diff/commit as needed:

       mds commit    (commits all config files changes)
       mds update    (grabs updates)

    3. Would be able to deal with per-machine variations...

       mds add /etc/httpd/ipconfig

    Some of my thoughts (not well developed because I know little  
about svk).

    Seems like for most configs, I could have a master set,  
effectively "trunk".

    For machines that have slight tweaks (lets say the gateway and  
the dns server is the same for all machines, but each one has a  
different ip address). So the trunk config file would look like this:

address=192.168.1.2
dns= 16.17.18.19.20
gateway=192.168.1.1

   Then each machine specific file could get stored on a branch by  
hostname, and would have a change like the following:
<
address=192.168.1.2
-------
address=192.168.1.3
 >

   So questions:

    1. Is anyone doing anything like this? What do you think the  
gotchas would be? How would you set this up?

    2. The example above grabs everything in /etc, then removes the  
stuff you don't want. Is there an easy way to grab only the things  
you DO want?

  Pierce