On May 20, 2006, at 05:25, Nico Kadel-Garcia wrote:
>>> Possible conclusions one can draw from this:
>>>
>>> * Mac OS X 10.4 is broken.
>>> * Resource forks cannot be used with Subversion.
>
> Or the more correct conclusion:
>
> * Resource forks are a bad idea, corrupting software and
> filesystems willie-nillie.
Yes, resource forks are a bad idea today, because of the many and
varied unexpected situations one can run into when trying to
interoperate with software that is not aware of resource forks
because it originated on non-Mac systems (not because they corrupt
anything, which they don't).
>>> The only solution I can suggest is to place your resource fork-
>>> containing files on a disk image, and check the disk image into
>>> Subversion. You'll no doubt be able to see why that's less than
>>> ideal. And the other solution is to use Mac OS X 10.3.x or
>>> earlier and
>>> never upgrade.
>
> It's not the OS. It's the file-system, which admittedly may be
> dependent on the OS. What does MacOS these days do with FAT32 and
> other, simpler file systems?
Mac OS X (all versions, as far as I remember) will create
files ._whatever to store resource fork data if the file contains a
resource fork and is copied to a file system like FAT32 or pretty
much anything other than HFS or HFS+ which cannot natively handle
resource forks. I know of no way to disable this "feature."
When I edit PHP source files on our company's Linux server via a
Samba share on my Mac, my text editor TextWrangler (the free version
of BBEdit) adds a resource fork to each file, to store the position
of the window and other settings. These show up on the server as ._
files. I installed a nightly cron job on the server to delete them.
<shrug>
At least Mac OS X's creation of .DS_Store files in every directory
can be suppressed on mounted servers using TinkerTool.
What's new in Mac OS X 10.4 is that the rm, cp, mv and other similar
commands have been modified to simultaneously affect the ._ files.
This is what makes Subversion broken now in this case, and this is
why I suggested 10.3.x or earlier as a workaround.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 20 20:50:39 2006