On Mar 14, 2008, at 05:07, Björn Blissing wrote:
> I am trying to set up a SVN repository for the projects we are
> working on. If we look at the projects at the directory level they
> are organised like this:
>
> ProjectA
> SubfolderA
> SubfolderB
> SubfolderC
> ProjectB
> SubfolderE
> SubfolderF
> SubfolferG
>
> My problem is that SubfolderA and SubfolderE should be exactly the
> same, ie. a subproject so if any user changes a file in Subfolder A
> these changes should appear in SubfolderE as well when the user
> commits his changes.
>
> So the logical structure is more like
> ProjectA
> ProjectC
> SubfolderB
> SubfolderC
> ProjectB
> ProjectC
> SubfolderF
> SubfolderG
>
> How should my SVN repository be organized to best suit this
> requirement? Of course each project (A, B and C) should be able to
> have its own branches.
I recommend:
/repository/
ProjectA/
trunk/
SubfolderB/
SubfolderC/
branches/
tags/
ProjectB/
trunk/
SubfolderF/
SubfolderG/
branches/
tags/
ProjectC/
trunk/
whatever/
branches/
tags/
In ProjectA/trunk and ProjectB/trunk, set svn:externals to pull in
ProjectC/trunk, or better yet, a specific tag of ProjectC.
http://svnbook.red-bean.com/en/1.4/svn.advanced.externals.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-14 11:33:13 CET