You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Judah Frangipane <ju...@t8design.com> on 2006/03/13 19:59:19 UTC

SVN Trunk, Branches and Tags directory structure question

Is there any reason I should *not* have all my files in the root of my
repository as long as I have the branches and tags directory the root as
well? I can't really think of a reason the following setup would not
work as well. 

 

Recommended Structure

 

 

/myProject

/myProject/tags

/myProject/branches

/myProject/trunk/[project folders]

/myProject/trunk/[project files]

 

 

Desired directory structure:

 

/myProject

/myProject/tags

/myProject/branches

/myProject/[project folders]

/myProject/[project files]

 

I just dislike the thought of changing the path on my projects from:

 

/myProject/[my files] 

/myProject/trunk/[my files]

 

...knowing all my class paths will have to be updated (increasing the
possibility of something breaking)... So if you don't see anything wrong
with my desired directory structure please let me know. TIA,

 

Judah


Re: SVN Trunk, Branches and Tags directory structure question

Posted by Andy Levy <an...@gmail.com>.
On 3/13/06, Judah Frangipane <ju...@t8design.com> wrote:
> Is there any reason I should *not* have all my files in the root of my
> repository as long as I have the branches and tags directory the root as
> well? I can't really think of a reason the following setup would not work as
> well.
>
> Recommended Structure
>
> /myProject
>
> /myProject/tags
>
> /myProject/branches
>
> /myProject/trunk/[project folders]
>
> /myProject/trunk/[project files]
>
> Desired directory structure:
>
> /myProject
>
> /myProject/tags
>
> /myProject/branches
>
> /myProject/[project folders]
>
> /myProject/[project files]

You're now making the tags and branches subdirectories of your actual
codebase if you do this, aren't you?  But they really aren't - you
want them to be copies of that codebase, right?  And, you'll find
yourself checking out all tags and branches just to check out your
trunk code. Very, very inefficient.  Plus, if you tag /myProject,
you're now tagging your tags directory.  Which you probably *don't*
want.

> I just dislike the thought of changing the path on my projects from:
>
> /myProject/[my files]
>
> /myProject/trunk/[my files]
>
> …knowing all my class paths will have to be updated (increasing the
> possibility of something breaking)… So if you don't see anything wrong with
> my desired directory structure please let me know. TIA,

Why would you have to change your class paths?  Just check your
working copy out from /myProject/trunk instead of /myProject and you
should be set, yes?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: SVN Trunk, Branches and Tags directory structure question

Posted by Mark Phippard <ma...@softlanding.com>.
"Judah Frangipane" <ju...@t8design.com> wrote on 03/13/2006 
02:59:19 PM:

> /myProject
> /myProject/tags
> /myProject/branches
> /myProject/[project folders]
> /myProject/[project files]
> 
> I just dislike the thought of changing the path on my projects from:
> 
> /myProject/[my files] 
> /myProject/trunk/[my files]
> 
> …knowing all my class paths will have to be updated (increasing the 
> possibility of something breaking)… So if you don’t see anything wrong 
with my
> desired directory structure please let me know. TIA,

In your structure, you cannot make a tag or branch of /myProject.  When 
you do, it will also copy every other branch and tag that previously 
existed because they are beneath the /myProject namespace.

Usually the name of the root folder of a project does not matter.  If you 
have:

Checking out the contents of /myProject to a folder will result in the 
exact same local structure as checking out the contents of 
/myProject/trunk.  In other words, there is no trunk folder locally. 

If I have a "Project" that is comprised of several "sub-projects" then I 
use this structure.

/Project/trunk/Project1
/Project/trunk/Project2
/Project/trunk/Project3

etc...

Mark



_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________