On Tue, Dec 25, 2007 at 09:52:12PM -0800, [EMAIL PROTECTED] wrote:
On Sun, Dec 23, 2007 at 06:41:19PM -0800, David Brown wrote:
I use 'unison' to synchronize configuration files and other working data.

  http://www.cis.upenn.edu/~bcpierce/unison/

It's kind of like a bi-directional rsync.  It works best to use it in a
star configuration where one machine or directories holds the central
version, and when you move to a new machine, you always sync before and
after making changes.  It has support for resolving conflicts, but it is
easier if you don't have to use it.

Wait.  Why not just use git for config files instead?
One less app to learn right?

A revision control system is going to do a lot more than I want for the
startup files in my home directory.  I want synchronization and possible
conflict resolution for when I do something silly and edit in two places.
A revision control system is first and foremost interested in keeping a
history of every change that has been made.  Distribution of these changes,
even if they are getting a lot better at it, is still very much a secondary
task.

I could certaily use git for this purpose.  I would just create a simple
repo that everyone pushes or pulls from.  It would probably even keep track
of conflict resolution a lot better than 'unison' does.  But, any time I
make a change, I need to commit it, giving at least something for a
description.

Maybe having the history would be useful.  Also, something like git would
make it a little easier for one machine to have a variant that kept merged.
But, there is still overhead in tracking it all, and I'm not sure it's
worth it.

However, this task sounds like an ideal small environment to experiment
with distributed revision control.  There is data that changes frequently
enough, and is distributed enough to exercise the system, but there isn't a
large amount of data and changes to deal with.

If anyone other than Chris is interested in doing this, I can post more
information here.  Otherwise, I'll just talk to Chris it in person.

Dave


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to