On Jun 16, 2005, at 1:12 PM, Daniel Thompson wrote:
> Here's a tool that will let you examine what files have alternate
> streams: http://www.sysinternals.com/Utilities/Streams.html.
>
> It seems like it would be pretty tricky to generically support
> alternate
> streams / resource forks. If you have a Windows Subversion server,
> and a
> Windows client, sure, that could be done, but what if you have a Linux
> Subversion server, and Windows and Mac clients?
This was discussed earlier. The alternate streams would not be
accessible if the WC filesystem did not support them, but they would
be preserved such that the commit from such a WC would not remove the
alternate streams from the repository.
> What if a client is
> using the FAT filesystem?
They get what they deserve? Why should any software developed in the
last 10 years support such an archaic FS? Subversion won't run on my
Commodore 64 either. Backwards compatibility is often simply not
worth it. (e.g. the 8.3 file naming hacks that are still present in
Windows)
> What if you want to burn the files to a CD (I
> don't think the ISO filesystem will get the alternate data streams)?
Irrelevant, since a CD is not a practical medium for a WC.
> It
> seems that this is not going to be practical to support because
> different filesystems have different implementations of alternate data
> streams--it's filesystem-specific. Unfortunate, but true.
As others have pointed out, so are symbolic links, but subversion
supports them (though that was a mistake IMHO, since such usage
pretty much always results in broken WCs on the most popular
supported platform). In this case I think the issue can be handled
well enough to make it worth doing.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 16 20:01:26 2005