On 3/13/06, Judah Frangipane <judah.frangipane@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
Received on Mon Mar 13 21:08:48 2006