OSX Resource forks in Unison 2.9.70
George Vilches <gav <at> thataddress.com>
2003-11-06 14:53:32 GMT
Hi,
Recently, we have compiled the newest version of Unison for OSX 10.3,
2.9.70. After a bit of tweaking (you probably need to account for
switching "pbxbuild" to "xcodebuild" in the Makefile, for instance), I got
the build to work, and synchronize locally (it crashed after a bit, but
the reason for the crash is unrelated to my actual question).
We have a Win2K server in which we need to sync files between. However, I
get the error saying that it won't sync because of resource forks (it
shows only one entry in the Unison list with "XXXXX", and I click on it
and see the error in the status box below). I've already familiarized
myself with all the naughties of resource forks that have been discussed
on this list, and why it might be a bad idea to try to sync to some fs
that doesn't support it. Unfortunately, we don't really have the option
of going to an UFS filesystem right now, and we're reasonably confident
that the files we want to move don't actually have resource forks
associated (or at least forks that have any data we care about, since
everything is done via DW's synchronize feature to our dev site, and if
the resource forks mattered, our dev site wouldn't work). That, and we
keep good backups, so if it fails, we're not screwed. :)
So, we wanted to know:
1) Are they any override flags allowing us to continue even though there
is the possibility of destruction? -force or force in the .prf didn't
seem to work (we did specify a root).
2) If no override flag exists, I'm willing to go code spelunking to
deactivate this and let you all know how it goes. But if you could direct
(Continue reading)