On Thu, Sep 9, 2010 at 8:00 PM, Itamar O <itamar...@gmail.com> wrote:
> On Thu, Sep 9, 2010 at 8:38 PM, Tech Geek <techgeek12...@gmail.com> wrote: > >> 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! >> > > Maybe I missed something in your scenario, > but I would simply have one trunk with PartA and PartB as sub-directories. > I'm with Itamar ProjectD ProjectD/trunk/PartA ProjectD/trunk/PartB Also, do read up on svn:externals if you haven't already. Cheers / Erik
