On 2-Aug-05, at 6:19 AM, Felix Gilcher wrote:
>
> I don't know how Scott handles his tags, but what we do is a
> directory structure such as:
>
> [hope my ascii-art does not break]
>
> repo_root ----
> |
> |--- project1
> | |------ trunk
> | |------ tags
> | |------ branches
> |
> |--- project2
> | |------ trunk
> | |------ tags
> | |------ branches
> |
>
> which makes tags and branches for each and every project live
> happily together, even if they carry the same name. The thing I
> like about it that it enables you to things like
>
> repo_root ----
> |
> |--- project1
> | |------ subproject1 (libs)
> | | |------ trunk
> | | |------ tags
> | | |------ branches
> | |
> | |------ subproject2 (app)
> | |------ trunk
> | |------ tags
> | |------ branches
> |
> |--- project2
> | |------ trunk
> | |------ tags
> | |------ branches
> |
>
> which very nicely shows which projects are closely related but may
> still be used independ of others.
I do the same sort of thing, but for project1 I would probably keep
the trunk,tags,branches folders between 'project1' and the
subprojects. If they are that closely related I want the convenience
of checking out all the sub-projects in one step from project1/trunk,
and I want to tag them together, etc. But we are fairly flexible
with the structure here and so occasionally the 'trunk' folder is at
a different level depending on the specific project.
I've also use svn:externals to make it easy to check things out in a
case where the 'trunk' folders are at the subproject level.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 2 14:59:19 2005