This feature of VSS is quite dangerous, as the shadow copy can
easily get out of sync if there are any network failures between the
client and the server the shadow folder is on. These errors almost
always happen transparently since the shadow folder is managed
transparently and the programmers didnt feel like telling us when Bad
Things Happen (tm). You are better off labeling the files and grabbing
by the pinned versions from a script on a regular basis (which is more
in line with what you have to do with other source control programs).
When the script dies you know something is wrong, other than odd
incompatibilies due to usage of the shadow folder (depending on what you
are using it for, i.e. binary documentation, this might or might not be
a problem.)
The most common case is: If the files in the shadow file are locked
(i.e. opened by a third party) they will also not be overwritten. You
could make the shadow folder a read only network share, but then people
can't update the shadow folder with their check-in's since the client
does that work . . . All in all its just broken.
C. Michael Pilato wrote:
>Early Ehlinger <earlye@respower.com> writes:
>
>
>
>>In VSS I was able to set up files that were "shared," which is similar to
>>the SVN concept of copy-via-hardlink. The difference is that as the
>>original file is updated, the shared-version keeps pace, whereas an SVN
>>copy-via-hardlink file retains the "old" version.
>>
>>Does the same functionality exist in SVN, and I'm simply missing it?
>>
>>
>
>No, it doesn't really exist. I mean, you can *kinda* get this
>functionality using svn:externals, but not at the granularity of a
>single file. If only Subversion could version soft-links...
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 15 22:07:42 2004