[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

help with a particular layout and deploy config

From: Lucas Stephanou <domluc_at_gmail.com>
Date: 2007-08-16 22:14:28 CEST

Hi,
This is my first msg to this list of much that are come.

As much others, I'm switching from cvs to svn and I have some questions that
maybe you can help me.

My project consist that 4(four) subprojects, the name of project is SSS, and
subprojects are ga, gb, gc, gd.
The basic tree look like this:
  SSS
   |--GA
   |----sources
   |------PHP
   |--------module_a
   |----------dir_a
   |------------file1.php
   |------------file2.php
   ......
   |------JAVA
   |--------module_a
   |----------dir_a
   |------------file1.java
   |------------file2.java
   .....
   |--GB
   |----sources
   .....

as you can see, that's a very big project, with more than one milion of code
lines.

but, only this is not a problem, my real problem it's a way that I release
versions, don't exists a SSS package/versions, packages are made with
subprojects and each subproject as a manager and he decides what go in each
version of he subproject.

example:
John is manager of GB subproject, and he decide to make a package with a
bugfixes that involves
   GB/sources/PHP/module_b/file1.php
   GB/sources/PHP/module_b/file2.php
   GB/sources/JAVA/module_a/file2.php
   GB/sources/JAVA/module_b/file1.php
 and here come my question, how I can made this using subversion? how I can
mark this files to be part of my package.

ps.: I'm planning to use standards layout:
  SSS
   |-trunk
   |--GA
   |-branchs
   |--x
   |----GA
   |----GB
   .....
   |--y
   |-tags
   |--release1
   |--release2

well , some suggestions , ideias, anything at this moment can help me to
decide this.

sorry for my bad english, I hope that you understand

-- 
Lucas Stephanou
Received on Thu Aug 16 22:12:31 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.