I'm new to Subversion, I installed it and migrated a few projects from my
CVS repository yesterday. So far it's working fine (congrats guys! Less
than a day using SVN and I'm not going back to CVS!) but I've encountered a
problem.
I usually work in Linux, where I have a structure equivalent to this
/build/build.py
/project1/build.py -> ../build/build.py
/project1/foo.cpp
/project2/build.py -> ../build/build.py
/project2/bar.cpp
I have build, project1 and project2 in SVN. In linux everything works fine.
However when I dual boot to Windows (sorry, I have to, our users use
Windows) and I check out the projects, I don't get the symlinks or an
usable equivalent. I know, I know, Windows doesn't support symlinks and
shortcuts are a joke. However, in an interesting bug-or-feature dilemma,
CVS did what I wanted it to do - it gave me my scripts, instead of a link.
I understand the limitations of Windows and I know this isn't a problem
with SVN per se; what I'm trying to figure out is how to work around this
limitations in the least horrible way. What I need essentially is to keep
using my symlinks as they are in Linux, but have an usable and automated
alternative in Windows. For example, a server-side pre-checkout hook (does
that even exist?) that tries to interpret the symlink locally (to the
repository) and give me the pointed-to file in Windows. Or a client-side
post-checkout hook (does that even exist?) that manually replaces the links
with their contents (assuming I also check out /build in my Win32 working
copy)
Thanks in advance!
--Gabriel
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 31 04:39:50 2006