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

Repository Structure

From: Muhammmad Mateen <m.mateen_at_udld.biz>
Date: Thu, 29 Oct 2009 13:19:15 +0500

Hi guys,

 

I had a question about the recommended directory structure of my repository
in SVN. We've developed an ERP system which is composed of 12 modules. Each
module resides in its own directory except there is a shared folder
"CommonFiles" which contain files shared by all modules. It looks like as
under:

 

CommonFiles

Module1

Module2

Module3

..

..

Module11

Module12

 

If I don't have this shared "CommonFiles" folder then the best structure
would be to index the repository by Project so that I'll have standard
"branch", "tag" and "trunk" folders in each module. But, the problem in
doing this with "CommonFiles" folder is that if I create a branch of a
module then I'll have to create branch of "CommonFiles" as well and thus
will have to update the patch of Common Files to point to the Branch
"CommonFiles" folder. I'll have to do the same when I re-integrate my branch
into trunk.

 

If I index my repository on branch folder then the problem is that I'll be
creating branch from the trunk for whole repository while need to work on
only one module. The same would be a problem when I need to tag a release as
the releases are done module wise.

 

I would appreciate if someone could suggest a better approach.

 

Regards,

_________________________________________

Muhammad Mateen

IT Controller

UDL Distribution (Pvt.) Ltd.

14-H, Block-6, P.E.C.H.S., Karachi-Pakistan

Ph: 111-555-444.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2412424

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-29 08:18:26 CET

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