I think I am beginning to undestand what you are suggesting.
Right now I am in process of implementing this setup. At this point nothing
exits - no ProjectD, no PartA and no PartB. So I will try to summarize what
I have undestood so far:
1. All our SVN repositories lives under the following location:
2. Now each of the Project directories - Project A, Project B and Project C
are SVN repositories of their own (TortoiseSVN->Create Repository here)
3. Now Mr. ProjectD comes along with has two sub-parts - PartA and PartB.
So I create a new repository ProjectD (TortoiseSVN->Create Repository here)
under this (correct?):
and then create two directories (with their own tags, branches and
trunk) underneath ProjectD (all using SVN commands) like this:
Note that Part A and Part B are not their individual repositories. They are
just directories that live under ProjectD which is a repository.
4. Let's say now PartA and PartB code development begings and at some point
a tag is created for each of their release:
Now let's say the output of Part A - PartA.xcf and output of Part B -
PartB.xcf are concatenated into a file called PartAB-R1.xcf.
Q1. At this point I would somehow like to store this file
(PartAB-R1.xcf) into my SVN repository (ProjectD). What would be an ideal
location (logically) to store such a file. Should I be doing any kind of
merging from tags (REL1.0) of PartA and PartB to create another node called
"Combined-REL-1.0" or something like that. I would like to avoid this if
Q2. Also when somebody checks out ProjectD I would like that it pulls the
PartA and PartB revision history also so that users cab see the "Revision
Graph" of PartA and PartB together using the TortoiseSVN client.
I hope I am able to describe the whole scenario to you all.
Received on 2010-09-09 23:37:20 CEST