I'm considering hardlinking config files into a working copy of my SVN config repository. Is there any reason why not to manage config files this way?
Assume /home/user/confmgr/confs is a working copy of my config repository. Then I could hardlink config files as follows-
ln /etc/php.ini /home/user/confmgr/confs/php.ini
ln /etc/httpd/conf/httpd.conf /home/user/confmgr/confs/httpd.conf
Then when I need to edit a config file it's this simple
cd /home/user/confmgr/confs
vi httpd.conf
/sbin/service httpd configtest
/sbin/service httpd graceful
svn commit -m 'adding virtual host to httpd.conf for new project'