Re[2]: Project Organization

WN> Hi Bojan,

WN> Why are you considering using multiple repositories? Server
WN> performance or logical separation?

WN> If you are doing it for logical separation, you might consider just
WN> putting the different projects into different top-level directories.
WN> Then, individual developers can checkout just the directory for the
WN> project they're working on, but branching and tagging can easily be
WN> done across multiple projects if desired.

WN> You might also want to look at the svn:externals property, which is
WN> described in fairly high detail in the Subversion book. Using
WN> externals to link a project to other projects may be sufficient for
WN> what you want to do.

WN> - -Bill

  If I understand correctly, even with the svn:externals property, I
would have to somehow match revision numbers of shared projects and
applications.

  Say this is the organization:
    - rep1/shared
           sh1
           sh2
           
    - rep2/project1

  Now, when I need revision 341 of project1 repository, I must be aware that it
used revision 15 of shared repository. If there are other repositories
(like separate repositories for each third party library), the number
of revisions to track will increase. Is my understanding correct, or
can this be automated in some way?
  
  Regards,
     Bojan Resnik

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 11 11:52:58 2004