B. Smith-Mannschott wrote:
> I suspect, though I can not prove that the problem is this:
>
> (1) In order for the resource fork ._README to exist, the data fork
> stored in README must exist, even if it has length zero.
>
> (2) As far as subverison is concerned, ._README and README are just
> two separate files. It may, when it's millin garound in its
> administrative directories somtimes choose to move or create ._README
> before the corresponding README, thus causing the operating system to
> complain loudly.
Oh for pity's sake. Do *NOT* use Mac partition types with resource forks for
anything but local files, use Network file systems with types like SMB or
NFS to avoid that for now. This whole resource fork thing has been a
destructive force since Apple started using it, years ago.
> I don't have my mac in front of me right now, but I suspect that
>
> $ touch FOO
> $ touch ._FOO
>
> will work on a UFS volume, while
>
> $ touch ._BAR
> $ touch BAR
>
> will not. Can someone verify?
>
> there's an alternate notation for accessing resource forks from the
> shell in OSX, but it's likely to just confuse svn even more because it
> makes it look like FILE is a directory, even though it isn't:
>
> FILE (data fork)
> FILE/rsrc (resource fork)
>
> // ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 19 14:13:49 2006