At 08:07 PM 11/10/2002, Karl Fogel wrote:
>Do you remember exactly how you arranged things (that is, what was
>switched where)? I wonder if you didn't accidentally point some
>subdirectories at different repositories, or something... Anyway, a
>complete description of your repository and working copy situation
>will probably clarify here.
The correct directory structure looks like this:
/defender (base project)
/defender/common (part of defender base project)
/defender/client (subproject of defender)
/defender/server (subproject of defender)
/defender/neo_modules (base project)
/defender/neo_modules/neo/defender (subproject of neo_modules)
So, here's the repository configuration:
/home/subversion/ is the top level of the repository
/home/subversion/trunks was created by 'svn mkdir'
/home/subversion/trunks/defender was created by 'svn import'
/home/subversion/trunks/defender-client was created by 'svn import'
/home/subversion/trunks/defender-server was created by 'svn import'
/home/subversion/trunks/neo_modules was created by 'svn import'
/home/subversion/trunks/neo_modules-neo-defender was created by 'svn import'
As each of the subprojects were imported, a "stub" empty directory was left
behind, to be attached by 'svn switch'. So, my checkout script does this --
svn co file:///home/subversion/trunks/defender defender
(this gives /defender and /defender/common, as well as empty directories
/defender/client, /defender/server, /defender/neo_modules)
svn switch file:///home/subversion/trunks/defender-client defender/client
(this populates /defender/client)
svn switch file:///home/subversion/trunks/defender-server defender/server
(this populates /defender/server)
svn switch file:///home/subversion/trunks/neo_modules defender/neo_modules
(this populates /defender/neo_modules, which includes an empty directory at
svn switch file:///home/subversion/trunks/neo_modules-neo-defender
(this populates /defender/neo_modules/neo/defender)
All this checking out and switching works great. I can svn status -u to
see what is switched and what is not, etc. The problems come after I've
started to make changes and try a status, update, or commit.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Nov 12 13:52:50 2002