Nico Kadel-Garcia wrote:
> Richard Stephens wrote:
>> thanks, thats helpful. We do have machines running 10.3, but one of
>> the machines that will be accessing the repository is an intel imac,
>> and 10.4 isn't available on intel.
>>
>> Is there a way to either make the OS not move the resource forks, or
>> to make subversion check out the ._ files first/
>>
>> -Richard
>>
>> On 19/05/2006, at 8:31 PM, Ryan Schmidt wrote:
>
>>> On May 19, 2006, at 08:00, Richard Stephens wrote:
>>> On Mac OS X 10.4, Apple "helpfully" modified the built-in commands
>>> which move and copy and remove files, so that they also move and
>>> copy and remove the separate resource fork files on filesystems
>>> like UFS where they exist. So as soon as Subversion tells the OS to
>>> move foo from within the .svn directory to outside of it, the OS
>>> "helpfully" moves the ._foo file along with it. Subversion does not
>>> know that this has occurred, and thinks ._foo is still in the .svn
>>> directory waiting to be moved. So Subversion tells the OS to move
>>> the file ._foo, and—heavens to Betsy—it's not there and an error
>>> occurs.
>>>
>>> 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.
Maybe, but that doesn't help people that have to deal with them.
Furthermore, Mac OS X doesn't actually use resource forks any more, it
emulates them with extended attributes, which are available in many
other operating systems. So it is a pretty unfortunate that Subversion
doesn't properly handle them.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 21 18:21:10 2006