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

Project Organization

From: Bojan Resnik <resnikb_at_swissinfo.org>
Date: 2004-09-10 23:52:21 CEST

  Hello,

  I am new to Subversion, having used VSS in the past. I have read the
Subversion book, and I like the Subversion way of doing things.

  However, I am having thoughts about reorganizing the projects, and
there is a conceptual issue which I cannot seem to resolve. Currently,
all the projects are in a single VSS database, but it seems to me that
it would be beneficial if each had its own Subversion repository. The
problem is that there is set of common projects, and all other
projects depend on at least one of these. The structure is similar to
this:

   - shared
       - sh1
       - sh2
       ...
   - project1
   - project2
   ...
   
   Both project1 and project2 depend on sh1, while some other
root-level projects have their own dependencies among the shared
projects.

   Conceptually, it seems that all shared projects should go into one
repository, and every project into a repository of its own. But,
Subversion commands work only within a repository, so working with
this layout would be a maintenance nightmare... Branching for a
release version would include branching from two repositories, and
many other tasks would require keeping track of two (or more) revision
numbers of different repositories... Or maybe I have misunderstood
something?

   Did anyone have similar problems, and what solution did you come up
with?

   Regards,
     Bojan Resnik

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 10 23:53:01 2004

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