> If I remember correctly, ClearCase supports symbolic links on both
> Windows and Unix-like systems. Ironically, unlike
> Subversion, ClearCase
> completely subverts the underlying client filesytem and installs its
> own. On Windows, to create a view (similar in concept to a working
> copy) of a Versioned Object Base (VOB), you must map a drive to the
> view, so unlike on Unix, the Windows ClearCase client does not allow a
> user to create a view rooted at any directory in the filesystem.
> However, the ClearCase client filesystem does support both symbol and
> hard links. Maybe Subversion should try to emulate the
> ClearCase model.
The view in ClearCase that you're talking about is called a dynamic
view. It creates a virtual file system based on the files checked out
to your local client (and stored in some hidden area on your hard drive)
and the repository's latest versions for that image.
However, ClearCase also has something called static views. This is very
similar to how Perforce / Subversion / CVS work: checkout to directory
of your choice, use the tools of your choice, check back in again. No
virtual file system. Now, how does ClearCase deal with links in a
static view? I have no idea. Does it copy the file twice to the two
different locations? If both files are modified on the same system,
does the CC client try to deal with the concurrent modifications? I
don't know.
--
Jay Glanville
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 5 17:14:26 2004