On Apr 15, 2005, at 10:25 AM, K. Richard Pixley wrote:
> Why is this:
>
> project1/trunk
> project1/branches
> project1/tags
> project2/trunk
> project2/branches
> project2/tags
>
> considered a better practice than:
>
> trunk/project1
> trunk/project2
> branches/project1
> branches/project2
> tags/project1
> tags/project2
>
> The latter would seem to be capable of branching or tagging project1
> alone, project2 alone, or project1 + project2 in combination where the
> former makes this considerably more difficult for aggregate operations
> like builds, tar'ing, find's, etc.
If a tag or branch of project1 + project2 together is a common
operation, the second layout is probably better for you. If the
projects are generally separate, it's probably better to use the first
layout, as it keeps thing logically more encapsulated. For instance,
if you wanted to see all of the tags for project1, you could easily
just list the tags directory for project1, without needing to sift
through tags from other projects. It also makes it easier if you ever
need to split the repository into two or more repositories.
Also, remember that those two layouts are just recommendations. There
is nothing limiting you to just using one of those two. For example,
if your projects are mostly encapsulated, but you occasionally want to
make a tag that includes two projects, you could use the first layout,
but also create a top-level /tags directory that would be used for tags
of multiple projects.
-Bill
>
> --rich
>
> ---------------------------------------------------------------------
> 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
Received on Fri Apr 15 17:43:50 2005