Re: repository directories layout

If you only will ever have a single project in the repository this is
probably fine. If you have more than one and use 3rdparty libraries
and tools you probably want something a little more exotic.

We're still migrating but we'll end up with something like

repo/
    dev/
        3rdparty/
            sun/
                jdk1.4.3_11/
                jdk1.5.0_01/
            sometool/
                sometool_1.0/
        mainproject/
            trunk/
                3rdparty/
                    jdk/ <--- cheap copy from /dev/3rdparty/sun/jdk1.5.0_01
                    sometool/ <--- cheap copy from
/dev/3rdparty/sometool/sometool_1.0
                src/
                    ...
            branches/
            tags/
        olderproject/
            trunk/
                3rdparty/
                    jdk/ <--- cheap copy from /dev/3rdparty/sun/jdk1.4.3_11
                    sometool/ <--- cheap copy from
/dev/3rdparty/sometool/sometool_1.0
                src/
                    ...
            branches/
            tags/

These aren't actually the names of our folders but you get the idea I
hope. Two projects that can independantly change their required
libraries without affecting each other yet the repository only gets
the library checked in once and then svn-copied to the other
locations.

Initially it's just a dev repository but we're expecting to have a
customer services team in there as well. I've added the 'dev' folder
level to allow for this distinction.

Of course checkouts will simply do a

svn co svn:.../dev/mainproject/trunk mainproject

so other than the checkout they don't really deal with the extra folder depth.

Of course, I'm still migrating so I'm hardly a subversion authority -
can people 'in the know' yell out if they see any issues with this.

--
Aaron
On 5/10/07, H.S. <hs.samix@gmail.com> wrote:
>
> Hello,
>
> I have just started to use Subversion (changed over from CVS) and wanted
> some clarifications regarding the directories layout.
>
> I have searched google and it is a common suggestion to have trunk,
> branches and tags directories in the repository:
>
> RepoName
>     tags
>     trunk
>     branches
>
>
> Now, what I did was, first created the repo RepoName with svnadmin
> command and then made the three directories using svn mkdir commands. I
> then checkout the repo into my local machine, and then copied the source
> code into trunk directory and then added all the files in that directory
> to the repo. Then I committed the repo back. I can then checkout the
> repo and I get the directory with repo name and the three directories
> (where trunk has the source code). Am I doing it right? If yes, then
> other programmers just make their changes in the source files in the
> trunk directory and commit their changes back?
>
> The other method I understand is to create the three directories in a
> local directory. Put all the source files in trunk directory and then
> create the repository with all the three directories in that.
>
> Are both the methods equivalent as far as the directory structure is
> concerned?
>
> If you can give some other pointers regarding creating the new
> repositories (I checked the red book, it talks about the directory
> structure but doesn't give an example showing exactly what to commit
> while creating the repo), that would be an added bonus.
>
> thanks,
> ->HS
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org