Re: repository layout

Have you tried this approach?
AFAIK, the first time you co, a .svn dir is created, which konws the
path of ur working copy on the repository. So for future cos/cis you
just have to type
$>svn ci -m "checking in"
and to retreive the latest files from the repository into your existing
svn workign copy
$> svn update
and so on. So you only have to give the full src and dest path the first
time you co.
I use the trunk/myproject layout, but I don't think its a rule, its just
a guideline for the repository layout.
Do try it and let me know if it works.

Thanks,
Karan

Jean-Pierre Sevigny wrote:

>
> Hi,
>
> I'm reading the best layout for projects is to be:
>
> projectA/trunk
> projectA/branch
> projectA/tags
>
> projectB/trunk
> ...
>
> I understand the principle behind it, but i have a problem with this:
> if some tools (makefile, etc..) depend on the path to be
> projectA/src
> projectA/lib
> ...
>
> This means that everytime someone issues a co, he must specify the
> destination [PATH]?
>
> I find this not very convenient.. is there a better way?
>
> Thanks,
> JP
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

-- 
CM II
Resolution Systems Inc.
/-- never compromise. what if you compromise and lose? --/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org