RE: best way to add /trunk /tag /branch to existing repository

> OK, after using SVN for many years, and CVS for many prior to that, I'm
> just not understanding the difference between
>
> > /bbook/fnfapp/trunk
> > /bbook/fnfapp/branches
> > /bbook/fnfapp/tags
> > /bbook/fnflib/trunk
> > /bbook/fnflib/branches
> > /bbook/fnflib/tags
>
> and
>
> > /bbook/trunk/fnfapp/
> > /bbook/tags/fnfapp/
> > /bbook/branches/fnfapp/
> > /bbook/trunk/fnflib/
> > /bbook/tags/fnflib/
>
>
> I mean, other than the obvious that one has trunk|tag|branches above
> the
> component/library root, and the other has it below.
>
> Is there a real difference in practice? Or is it just convention?
> Seems to me that with the structure I was thinking about, I can just
> "get the latest truck of everything" and be happy.

This way you can branch the fnflib without branching fnapp. You can also tag each project individually. While, you can still in theory do it with the second layout... the first layout makes much more sense if you have many projects in a single repository.

> Having the trunk|tag|branches below always struck me as making them
> more
> visible.

They are just as visible the first way above. When you browse the repository you very top level will be all of your projects. If you drill into a project folder you will see the trunk/tag/branches for that specific project.

BOb

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2392971

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-09 17:42:31 CEST