repository layout

[Gerard Marcel <me...@gmail.com>]

I am a newbie at svn, but i have been using cvs for 2 years.  I would like
to keep the layout from cvs which is:


/var/repos/project1
/var/repos/project2

In svn, I would like the following:

https:/localhost/svn/repos/project1
https:/localhost/svn/repos/project1/trunk
https:/localhost/svn/repos/project1/branches
https:/localhost/svn/repos/project1/tags

The others should be the same.  Some base code will be used across projects
as well.  Is this possible?


Any help would be appreciated!!!



GM

Re: repository layout

[Florian Seydoux <fl...@gmail.com>]

Gerard Marcel wrote:
> I am a newbie at svn, but i have been using cvs for 2 years.  I would 
> like to keep the layout from cvs which is:
> 
> 
> /var/repos/project1
> /var/repos/project2
> 
> In svn, I would like the following:
> 
> https:/localhost/svn/repos/project1
> https:/localhost/svn/repos/project1/trunk
> https:/localhost/svn/repos/project1/branches
> https:/localhost/svn/repos/project1/tags
> 

Exactly; or to be precise, it would be:

https:/localhost/svn/repos/project1
https:/localhost/svn/repos/project1/trunk
https:/localhost/svn/repos/project1/branches
https:/localhost/svn/repos/project1/tags
https:/localhost/svn/repos/project2
https:/localhost/svn/repos/project2/trunk
https:/localhost/svn/repos/project2/branches
https:/localhost/svn/repos/project2/tags

It's better to start with the stuff in the right top-level folder (for 
eventual further dump filtering), but not mendatory,
and for the 'tags' and 'branches', you can start without them (just the 
trunk), and create them when needed.

As it's mentionned in many place, with svn you can choose the 
'directory-tree' that you want
(trunk can be called 'devel', tags 'snapshot', etc; they are just usual 
convention).

In addition, as you can rename and move stuff, you don't risk too much 
if you start with a bit "wrong" (or not conveniant) structure.

> The others should be the same.  Some base code will be used across 
> projects as well.

hum... depending on how is your build (local) tree, some killing details 
can be here.

If the base code is located in a different "project" (eg. 'shared'),
then it will take place in a
    https:/localhost/svn/repos/shared {/trunk,/tags,/branches}

from that, you have two choice to build your working copy:

1)
checkout the 'shared' part and 'project(1,2)' separately (separate WC),
but in a fixed relative position (eg: 2 shared must be two level up from 
project(1,2)).
The build will also be separated (you should buil the shared part, then 
the project)

2)
in project1 and project2, place a link (svn:external) to the shared part.
In this case, the shared part will be "duplicated" with every WC of 
project(1,2),
but the build process  can be much easy to manage.


... hum... I'm not sure that I'm really clear... (sorry)

regards,

florian

-- 
--------------------------------------------------------------------
Seydoux Florian, PhD
http://www.spinx-technologies.com
--------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org