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

How to organize a repository?

From: Chris <shef31_at_yahoo.com>
Date: 2007-06-21 22:07:49 CEST

I'm struggling to decide how to organize our projects. From a high
level, here are the directories in our system:

/src -- the main source directory
/old_src -- source for an old version, still making bug fixes
/src-client1 -- source code for a particular client

/deploy -- readme.txt, license.txt for main proj
/lib -- 3rd party libraries, shared by all
/doc -- end-user documentation
/design_docs -- internal, developer documentation

/webapps -- client-specific web applications
/webapps/client1 -- webapp for client1
/webapps/client2 -- webapp for client2

/data -- data dir. big, should not be stored in svn
/data/client1 -- data for client1
/data/client2 -- data for client2

/test_database -- test data, used by unit tests

We use Eclipse for development.

Questions:

Should every directory be a project, with its own /trunk, /branches, and
/tags subdirectories?

This seems like a lot of directories, plus it isn't clear to me how to
keep releases in sync. Suppose /src release number 1.5 depends on
certain versions of 3rd-party libs, and relates to docs at a certain
revision?

Should I have everything in one giant repository?

Can someone post some sample directory and repository layouts?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 21 23:13:11 2007

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