Hi!
I asked about structuring of nested releases last week (and got good
answers, thanks Hari!).
I am now more concrete. Is the structure below good?
The component tags (eg comp1/tags/component/0.5) contains external
references to corresponding subcomponent releases (eg
comp1/tags/subcomponents/comp1_dll/0.3).
The project tags (proj1/tags/1.0/src), and trunk, contains external
references to corresponding component releases (eg
comp1/tags/component/0.5).
I havent shown separate files, just directories.
Is this a normal way to use subversion?
Is this structure worse than others regarding handling branching?
If not; can you suggest changes to my structure?
And, if ok on this list; will this structure work well together with TRAC?
repos/components
+---comp1
¦ +---branches
¦ +---tags
¦ ¦ +---component
¦ ¦ +---0.5
¦ ¦ +---comp1_dll
¦ ¦ +---comp1_interface
¦ ¦ +---comp1_internal
¦ ¦ +---comp1_main
¦ ¦ +---comp1_test
¦ ¦ +---subcomponents
¦ ¦ +---comp1_dll
¦ ¦ ¦ +---0.3
¦ ¦ +---comp1_interface
¦ ¦ ¦ +---1.1
¦ ¦ +---comp1_internal
¦ ¦ ¦ +---0.10
¦ ¦ +---comp1_main
¦ ¦ ¦ +---0.7
¦ ¦ +---comp1_test
¦ ¦ +---0.3
¦ +---trunk
¦ +---comp1_dll
¦ +---comp1_interface
¦ +---comp1_internal
¦ +---comp1_main
¦ +---comp1_test
+---comp2
+---branches
+---tags
¦ +---component
¦ ¦ +---1.0
¦ ¦ +---comp2_check_configuration
¦ ¦ +---comp2_interface
¦ ¦ +---comp2_kernel
¦ ¦ +---comp2_test
¦ +---subcomponents
¦ +---comp2_check_configuration
¦ ¦ +---0.5
¦ +---comp2_interface
¦ ¦ +---0.7
¦ +---comp2_kernel
¦ ¦ +---0.3
¦ +---comp2_test
¦ +---0.9
+---trunk
+---comp2_check_configuration
+---comp2_interface
+---comp2_kernel
+---comp2_test
repos/projects
+---proj1
+---branches
+---tags
¦ +---1.0
¦ +---src
¦ +---comp1
¦ +---comp2
+---trunk
+---src
+---comp1
+---comp2
Many thanks
Henrik
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 21 17:47:32 2007