Zieg, Mark wrote:
>>I have to sync two CVS repositories located on two non-
>>connected networks. (yep, this means tape/CDROM transports,
>>I know it sounds silly). I was wondering if there is a
>>better way than creating incremental tar files on both sides
>>and applying them on the other side. Luckily, the chances
>>that two persons from the two sites are working on the same
>>file are minimal, but I would like to prevent possible sync
>>errors if it occurs.
If you MUST do this (and it is almost certain that you do not need
to, but that's another story), then please examine two messages from
the archives of this list entitled "How I repaired my repository"
dated 30Jun02 - my summary of how I repaired a corrupt repository from
a good sandbox and Eric Siegerman's additional suggestions. In your
case, it becomes "How to sync your repository", the "restored archive"
is your "repository to be updated", and the "preserved sandbox" is
your "sandbox created from the other repository".
Note that there is significant potential for disaster. Note that you
will have to do this again, in the other direction. Note that CVS was
not designed for multiple repository operation. Note that this is
generally a bad idea. Is a pattern emerging here?
> Silly or not, I'm going to have to do the same thing in a week or so -- and
> it will probably become a regular part of our CM process. In certain
> industries, the need for private, disjunct networks is an unbending fact of
> life.
We can categorize these industries as "industries which do not
understand computer security", and yes, we'll be stuck with them for
some time to come.
> I haven't come up with a solid plan for this that I liked yet, but I'll
> watch the list to see if anyone has a good existing method, and I'll share
> whatever I come with in-house...
As much as I discourage doing this, I am interested in whatever you
settle on.
/|/|ike
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
