Tangential question about bzr concepts

[Martin Pool]

On  1 Apr 2006, "Andrew S. Townley" <andrew.townley at bearingpoint.com> wrote:

> Thanks Martin.  However, my unclear comment was really to do with the
> space requirements.  I looked at Coda, but that isn't really what I want
> because it implies there is only one repository.  Why I was kind of
> "navel gazing" about bzr was so that I could isolate, say a directory
> tree, and then have that tree able to be sensibly merged in either
> direction from one client to two different servers.
> 
> I know it's possible if I use bzr as is, but the problem I have is the
> disk space usage for the revisions.  If I have a bunch of text files
> (e.g. source code), it isn't really that big of a deal, but where you're
> talking about managing word or other binary documents some of which are
> 20M a piece, it can quickly eat into your usable filesystem space.  I
> know bzr won't help me with the "inside merge", but at least something
> like bzr would keep things up to date.  In this case, there's no need
> (and in fact, I don't want) to have simply cached versions between the
> client and the server.
> 
> Anyway, like I said, I'm just thinking about the problem because I'm
> having some trouble managing some occasionally connected machines that
> effectively have two "homes" or none at all, depending on your point of
> view.  I don't know if I'm going to tackle the problem or not as yet,
> but if it was something I could do reasonably easily, then I might
> seriously consider devoting some time to it.

Unison is probably a good way to go for your purposes:

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

-- 
Martin