> trunk/components/componentA/
> branches/jlwasmer/components/componentB/
>
> or
>
> trunk/components/componentB/
> branches/jlwasmer/components/componentA/
>
> I need to change the makefile or create a new one.
>
> JL
The way to solve this problem is not to have your build system mirror how
your repository is laid out. You'd do:
svn co http://localhost/svn/repos/trunk/components components
svn co http://localhost/svn/repos/trunk/projects projects
and you'd end up with projects and components under the current directory.
Then if you wanted to have components come from a branch:
svn co http://localhost/svn/repos/branches/mybranch/components components
Now if you are checking out the ENTIRE repository, you will have the issue
you described, but doing this method you can have the components come from
where ever and put it all under 'pwd'. The thing is that
the /svn/repos/trunk vs branches is an internal mapping, you can externally
map it to anything you want. Perforce automates this for you with the
concept of a client map, but svn doesnt (yet?!).
To explain, in p4 you do something like:
//myrepo/trunk/make-support/... //client/make-support/...
//myrepo/branch/devo-1/componentA/... //client/componentA/...
etc
And the p4 will manage that for you.
Maybe this should be a post-1.0 feature add?
Regards,
-ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 3 00:13:54 2003