Hi all, new to the list with this question, but I couldn't find a
reference in the archives that's really relevant, and the FAQ doesn't
quite address it...
I did two things today. I updated the current release of TortoiseSVN,
and I added a Windows Vista symlink (yes, they really are symlinks) to
my working copy and did an "add". Given the FAQ (or rather,
frequent-feature-request, I guess) info on symlinks, I assumed it would
treat it as a regular file and end up with a copy in the repository,
which would be no great problem. However, the behaviour seems to suggest
that windows symlinks "half-work". I ended up with the commit aborting
saying "platform does not support symlinks" (I may have forgotten the
exact wordig) and an unclean working copy that wouldn't clean up (I
ended up cleaning it up by hand).
I've since replaced the symlink with a copy, but as far as I can tell
what happened was that the commit phase of the commit was entirely
successful in creating a symlink entry in the repository, and then it
barfed when trying to update after the commit. I think this because the
commit did increment the revision count, and did put the new versions of
everything on the server, but didn't increment the local copy revision
count (and left all the "lock" files in the .svn directories).
So, anyone any idea what's going on, and/or if this means we Vista users
might get more value out of our symlinks soon? Or should this question
be addressed to the core subversion devs, as it's really their libraries
that cause the behaviour?
Thanks,
Sam
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-11 16:11:51 CEST