I am moving to Subversion and I am having difficulty determining the
appropriate layout for the respository, which I will be converting from
VSS (yuck).
Currently, the respository contains many projects, which contain many
subprojects. There are also lots of things that expect a certain layout
on the hard drive: Makefiles, build tools, utility software, etc. This
is making it difficult to choose the appropriate layout:
======= #1: The elephant has many trunks =======
projectA/
trunk/
branches/
subprojectA1/
trunk/
branches/
subprojectA2/
trunk/
branches/
projectB/
.
.
.
- Branching and tagging work everywhere since this follows the
official Subversion recommendations.
? If a developer does a recursive checkout at "ProjectA/trunk" will
they get every single branch of all the subprojects?
======= #2A: The baby elephant =======
projectA/
subprojectA1/
trunk/
branches/
subprojectA2/
trunk/
branches/
projectB/
.
.
.
- Can only branch/tag files in the subprojects
? If a developer does a recursive checkout at "ProjectA" will they
get every single branch of all the subprojects?
======= #2B: The daddy elephant =======
projectA/
trunk/
branches/
subprojectA1/
subprojectA2/
projectB/
.
.
.
- Can only branch/tag files in the parent projects
======= #3: The default layout =======
projectA/
subprojectA1/
subprojectA2/
projectB/
.
.
.
- This layout matches the users hard drive exactly
- Recursive gets are easy
! This layout works with the existing build system we have in place
Anything else is going to require modifying build tools, Makefiles,
and various ancillary tools.
! No way to reasonably branch or tag
The last two points in "!" are the real issues driving this. The
question is also going to affect things.
Any suggestions would be appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 1 04:55:40 2004