Ryan: Thanks for the link, svk looks interesting. Unfortunately this is
not realistically an option if I would have to change the repo at work
since more people than just myself use this and it just wouldn't be
possible to change repos (not to mention losing 15000 revisions which
wouldn't go down well)
Lawrence: That is a good idea! I would most certainly do this if I
wanted the whole repo to be the same as the other, but I only want to
mirror part of it. I guess a script could use the repo path to decide
whether to commit to the other repo. The downside is I'd have to open up
my own repo which is a little risky. At the moment it's only accessible
via an ssh tunnel on a high port with access only via a strongly
encrypted pub/priv key pair, I'll bear this in mind, but I just can't
think of leaving an unencrypted key into my home on a server at work....
Perhaps I'll just have to periodically copy things over.... oh the
drudge of doing anything manually (gotta get a computer that writes
without me typing I guess... voice activated? too much vocal work. now
mentally activated I can dig... :-) )
Lawrence Stewart wrote:
> Ryan Schmidt wrote:
>> On Dec 8, 2006, at 06:19, Hari Sekhon wrote:
>>> i have a subversion repository at work and also one at home. The
>>> things I do
>>> at home and at work usually coincide since I never seem to stop
>>> working so
>>> I'd like to share some of my work between the two and keep files in
>>> repositories. This is also good from an off site backup perspective.
>>> I'd ideally like to be able to check in something and for it to go
>>> to both
>>> repositories at the same time, but failing that it would be
>>> sufficient to
>>> just be able to sync the 2 often. Bearig in mind that one repo will
>>> have some stuff I don't want in the other and vice versa...
>>> Thinking of the offsite replication point of view. This is an
>>> thing to do so I'm hoping I'm not the first person to have thought
>>> this and
>>> something has been done to accomodate it.
>>> Does anybody know if this can be done and if so how I could go about
>>> implementing it?
>> Subversion doesn't offer this. As of Subversion 1.4 there's a new
>> thing called svnsync, but that's only for making read-only copies of
>> a repository; you want both repositories to be writeable and svnsync
>> doesn't support that.
>> You may want to look into svk, which is based on Subversion and is
>> designed for distributed repositories. It may support the model
>> you're looking for.
> I'm not sure whether this would be technically feasible or not, but does
> anyone know if it is possible to install a hook (post-commit?) at each
> repository that, after a successful commit, performed a commit to the
> other repository? Assuming there's only ever work occurrng at one
> repository at any one time, there shouldn't be concurrency issues with
> rev numbers changing at the other repo, and it would allow both repos to
> remain readable and writeable (as opposed to using svnsync to make one
> only readable).
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Dec 11 11:04:22 2006