On Thu, Sep 9, 2010 at 8:52 PM, Geoff Hoffman <geoff.hoff...@jawa.com>wrote:
> > We have hundreds of trees, each with their own trunk/ branches/ tags/ in > one SVN repo. Works great. You may want to look at svn:externals. It may > require re-thinking how you're using SVN a bit, but the payoff can be big. > Basically you branch or tag anything shared, and load it into ProjectD using > Something like this? components components/comp1/[branches|tags|trunk] components/comp2/[branches|tags|trunk] components/comp3/[branches|tags|trunk] components/comp4/[branches|tags|trunk] components/comp5/[branches|tags|trunk] projects projects/projA/[branches|tags|trunk] projects/projA/[branches|tags|trunk]/comp1 -> components/comp1/[branches|tags|trunk] (with svn:externals) projects/projB/[branches|tags|trunk] projects/projB/[branches|tags|trunk]/comp2 -> components/comp2/[branches|tags|trunk] (with svn:externals) projects/projC/[branches|tags|trunk] projects/projC/[branches|tags|trunk]/comp3 -> components/comp3/[branches|tags|trunk] (with svn:externals) projects/projD/[branches|tags|trunk] projects/projD/[branches|tags|trunk]/comp4 -> components/comp4/[branches|tags|trunk] (with svn:externals) projects/projD/[branches|tags|trunk]/comp5 -> components/comp5/[branches|tags|trunk] (with svn:externals) Cheers / Erik > > cd ProjectD > svn propset svn:externals local/path path/to/trunk_branch_or_tag > > When you change files under path/to/trunk_branch_or_tag and svn up > ProjectD, changes come streaming in. > > HTH, > > Geoff > > > ----- Original Message ----- > From: "Tech Geek" <techgeek12...@gmail.com> > To: "Subversion Users" <users@subversion.apache.org> > Sent: Thursday, September 9, 2010 10:38:51 AM > Subject: Two trunks in one repository? > > > So the concepts of trunks, branches, tags are transparent to SVN. We are in > a situation where we might need to have two trunks in one SVN repository. > The reason is that we have a family of projects - say ProjectA, ProjectB, > ProjectC and so on, each one has it's own repository and have just one trunk > (normal setup) since the each of these project has just one part. > > But now let's say we have a ProjectD which has two sub-systems - PartA and > PartB whose code is 95% different. So we are thinking to have two trunks > inside the ProjectD repository. We would prefer not to create an individual > repository for PartA and PartB because we have decided to categorize each of > the repository based on the family of Projects - ProjectA, ProjectB, > ProjectC, ProjectD. > > Just wanted to know to get some thoughts from the experts on this mailing > list regarding this setup. Any gotachs I need to watch out for? > > Thanks! > >