Asked 2 years ago
I was thinking symlinks and unison, but svn is basically the same for this.
I've used cvs for this for ... probably a decade now. Helps to symlink down into a "dotfiles" directory, lets you update locally more sanely...
jtu, perturbed, lakmiseiru, jesse, coolworld, ntn, paigep, trs, Ian, cshiley, erin, Richie, Yoyo, androidqueen, Alex, eisenbud, aletta, transistorman, Schuyler, quince, roga, dzm, ternus, Lattyware, stilvoid, shadow
unison
I tried the svn solution, didn't like. I don't have anything better, though.
I put ~/dotfiles/ in svn and added a Makefile which runs m4 over them and installs the output as the dotfiles. The main problem I had with dotfiles committed directly in svn is I found myself wanting to customize them slightly based on the host, and not all dotfiles support that without an external macro tool. All that said, $HOME is also in svn. There are a lot of ignores. It is great.
Standardize on having your dotfiles in ~/dotfiles with a makefile/build-system to symlink them into place. Makes it easier to de-standardize a single dotfile without giving up on tracking them. Alternatively, give up on having dotfiles. Not customizing software is the new rock and roll.
Stick ~/.dotfiles into svn and symlink into it.
Stick dotfiles into a subdir of $HOME, have a script that copies or symlinks with $HOME.
I've found that darcs works very well in situations where you want to version control a pre-existing directory tree.
put them in ~/etc/ and write script to link them to $HOME. Then put ~/etc/ into svn.
That trick never works!
Copyright © 2006–2007 Best Practical Solutions, LLC • Contact us
If you make a stupid choice because a website tells you to, it's your own damn fault.