Directory Layout Guidance

["Ahmed, Omair (GE Oil & Gas)" <om...@ge.com>]

Hello,

 

We have an IT managed SVN environment. When the SVN admin created the
repository, it was with the "default" directory structure:

 

/trunk

/branches

/tags

 

However, we expect to implement a different structure. Something along
the lines of:

 

https://svn1hostname/svn/SVN_Repo/PROTOTYPE/

/APPLICATION_CODE

/trunk

/branches

/tags

 

/UTILS

/trunk

/branches

/tags

 

/CIMPLICITY

/trunk

/branches

/tags

 

1)      Can I simply delete the "default" structure and create the
directories as I've described above? 

2)      Is there anything special about the these dirs. (trunk,
branches, tags)? Can I just create them as I would any other directory
via the repo browser?

3)      Are there any disadvantages to laying out the directories as
described above? I want to avoid pitfalls that I am unable to foresee
right now.

 

Please advise.

Thank you.

Omair 

 

 

 

Re: Directory Layout Guidance

[Thorsten Schöning <ts...@am-soft.de>]

Guten Tag Ahmed, Omair (GE Oil & Gas),
am Freitag, 21. September 2012 um 22:23 schrieben Sie:

> 1)      Can I simply delete the "default" structure and create the
> directories as I've described above? 

Yes, or you move the current folders and/or copy them etc.

> 2)      Is there anything special about the these dirs. (trunk,
> branches, tags)?

Not technically, it's all convention based on names, technically they
are directories as any other one.

>  Can I just create them as I would any other directory
> via the repo browser?

Yes.

> 3)      Are there any disadvantages to laying out the directories as
> described above? I want to avoid pitfalls that I am unable to foresee
> right now.

That often depends on your product, environment, needed authentication
and authorization, what you want to merge where, shared code, what you
want and why etc. With more detailed description of you background,
e.g. why you don't want to use separate repos for your components, one
can help you much better. I personally prefer one repo per project,
with exceptions depending on things like assumed shared code, as may
be more efficient within one repo where things like efficient copies
work.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow