Has anyone else tried to work with Subversion Working Copies using NTFS
(Win2K&WinXP) Junction Points. I am having problems getting it to work.
Here is the setup
d:\wccopies\trunk\src
d:\wccopies\branch1\src
d:\wccopies\branch2\src
Where each 'src' directory is a full working copy checked out from
Subversion. Now due to build requirements that I can not control the 'src'
directory must be at the root of the drive, in my case d:
Now I realize that I can use svn switch to switch my working copy around but
I find it more convenient (esp. with 80 Gig drives today) to just have
multiple working copies available and use the one I need for the current
task. I set up a python script that will map '\wccopies\trunk\src' to
'\src' so the build process will work. If I need to move to a different
task on one of my branches the script can simply change the directory
junction to point to the correct working copy and everything is setup.
However it subversion does not seem to like directory junctions.
When I go in an change a file in the '\src' directory tree and then run 'svn
status' in '\svn' I get wrong information. At least I think it is wrong.
Here is the table of the results that I get:
Dir\Command Result
\src\svn status "~ S ." // obstruction and switch
\src\svn diff yields the correct
diff of changed files
\wccopies\trunk\src\svn status yields the correct
status report of changed files
\wccopies\trunk\\src\svn diff yields the correct
diff of changed files
Any ideas about what might be going wrong?
PS: Junction is a free tool that you can obtain from
http://www.sysinternals.com/ntw2k/source/misc.shtml#junction or if you have
the Win2K Resource Kit you can also use the linkd program to create the
directory junction.
Thanks
-Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 28 18:01:33 2003