I am writing a script to set up the development environment for the
developers on the project. The idea is that you do a svn co -N <root>
and then run the setenv.cmd (on Windows) script which then checks out
the needed subdirectories for the project.
So the flow is like this:
Svn co <root> -N
Setenv.cmd (which does):
- Check out <root>/development/vendor1/include
- check out <root>/development/vendor1/lib
- Check out <root>/development/vendor2/include
- check out <root>/development/vendor2/lib
...etc..
The problem is that when the developer does an 'svn up' in the WC for
<root> it gives an error saying that development already exists. So it
seems the WC for <root> does not know that 'development' came from the
same repository/directory.
I don't want to the developers just checkout the entire <root> because
there is a lot of stuff they don't need on a day-to-day basis. For
example the GUI developers really only need the documentation for the
GUI libraries we use, so I don't really want to copy that all down for
everybody by default.
Is there someway to tell SVN that the explicitly checked-out
subdirectories really are children of <root>?
I guess there is something fundamental that I am misunderstanding about
how I should use SVN.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 1 22:57:53 2005