On Jul 31, 2006, at 03:30, Nico Kadel-Garcia wrote:
>> On Jul 31, 2006, at 03:20, Nico Kadel-Garcia wrote:
>>> In particluar, are you using MacOS? There are some serious
>>> weirdnesses with resource forks that can be very tough to deal with.
>> What? Subversion makes no use of resource forks. Subversion on Mac
>> OS X should behave quite similarly to Subversion on *BSD or
>> Linux, from everything I've seen.
> I thought there were some reports here of difficulties when "svm
> move"ing files?
Perhaps you're thinking of this thread?
The problem was/is that for single-fork filesystems like UFS (or if
you have a working copy on a Samba share for example) then the
resource forks are represented as files whose names are "._" plus the
file's real name. But as of Mac OS X 10.4 Apple "helpfully"
automatically moves these files when you tell the OS to move the real
file. If both files are under Subversion's control, then you run into
errors when Subversion tries to move the "._" file but has already
moved the real file and the "._" file isn't where Subversion thinks
it is anymore. On the one hand it's Apple's fault for being too
helpful, and on the other hand it could be resolved by Subversion
doing file operations in alphabetical (instead of essentially random)
In any case, Subversion doesn't know about the resource fork and like
most CLI programs it will deal with files as data-fork only. When
used on Mac OS X's default multifork filesystem, HFS+, things
therefore work pretty well, for files that don't need resource forks.
If you check in a file, only its data fork gets checked in. When you
check out or update somewhere else, only the data fork will arrive.
And this is fine for most modern file formats where the resource fork
is optional (like my text editor which just uses the resource fork to
store editor settings like text font and size, window size and
position, and so forth -- which could be considered optional/
nonessential information so it's no problem this data is lost on
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jul 31 12:30:15 2006