[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Slave repository

From: Shem Page <Shem.Page_at_redvespa.com>
Date: 2007-01-24 02:06:43 CET

We are using subversion + the gui supplied by tortoise but my question
is really about the big picture of source control not so much
implementation of a particular product. Any advice will be helpful.

We have gone into partnership with another company in a different
country, and will be making changes to code which about 3 groups can
alter. The original repository is based elsewhere and due to connection
speeds, time differences and working relationships it is not practical
for us to work directly from it. So what we wanted to do was to check
out a slave copy (dated, tagged, whatever, at a stable point in time),
and then with that slave copy make it OUR repository stored on a server
which then in turn each one of our developers checkout and in from. We
need to be able to check our changes back into the original source when
we are ready but will be working off our own repository.


Foreign Server | Our Server
| Our Developers
Source 1.0 | Source 1.0 snapshot
| Source 1.0 checkout
<--regular check ins + updates --> |
 |<-- infrequent check ins and updates -> |

What I don't know about is this idea of checking out source and then
making that checkout a repository for others to check out. I know we can
export and import a project into a repository, but if we don't keep that
source control link between the two servers we will slide out of date
from their other developer groups. This is an untested working
relationship which is why we want source control where ever possible,
but we also some independence from other groups who may check in broken

Does this make sense? Is it something which is quite normal or are we
misunderstanding the way source control works?

Thanks very much for your advice.
Received on Wed Jan 24 02:07:05 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.