On 9/14/2006 7:49 PM, Garrett Rooney wrote:
> On 9/14/06, Duncan Murdoch <email@example.com> wrote:
>> On 9/14/2006 2:38 PM, Garrett Rooney wrote:
>>> On 9/14/06, Mark <firstname.lastname@example.org> wrote:
>>>> I am curious aboyut this new feature. I have a custom solution in
>>>> place to keep repositories synced between two servers, one bein the
>>>> master and one being the standby. I can switch roles between servers
>>>> as well. From my first read of what info their is about svnsync, it
>>>> sounds like the destination repository is only ever meant to be
>>>> read-only. Is that a hard and fast rule? Is there something I could
>>>> do to switch the roles of destination and source repositories?
>>> It's not a hard and fast rule, but to switch which repos is the master
>>> and which is the slave you'd have to manually go in and mess with the
>>> svnsync revprops on r0 of whichever is the slave. It's definately a
>>> hard and fast rule that you can only have one master at any given
>>> time. If you write to both the slave and the master then there's no
>>> mechanism for resolving the inconsistency.
>>>> A HOWTO for new features like this will help a lot. I'm willing to
>>>> write it with some help from the devs that put this feature together.
>>> Paul Querna put up a HOWTO for basic read-only mirroring on his blog yesterday:
>> Is there other documentation online somewhere? That page lists the
>> how-to, but not the things you can do with the sync'd copy.
> There's not a whole lot of documentation yet, but as far as "what you
> can do with the sync'd copy" I'm not sure what you're looking for.
> You can do anything with the copy that doesn't involve writing to it.
> Well, actually, you can write to it, but only if you never want to
> sync it again.
These are the things I'd like to do, off the top of my head:
- use the sync'd copy to tell me the history of a file in a working
copy from the original repos (when I'm offline, without access to the
original). Would I need to switch the WC, get the log, and switch back?
- use the sync'd copy instead of having the text-base originals for
the purpose of doing a "revert", to save disk space.
- check out a read-only working copy, and be warned if I tried to use
it in a dangerous way (e.g. by committing from it or otherwise treating
it as if it was from a regular repos).
- be able to switch from the working copy checked out above to the
original one at the appropriate revision.
- be able to make a backup of a repository when I have read access,
but not administrative access. I would have thought this was the main
idea, but then the description of how to convert between master and
slave makes it sound as though it's not.
I guess I just don't get the point of svnsync yet.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 15 02:01:33 2006