Hi Alastair,
If you are investigating resource fork handling options, please have a look at what I have done here a little while ago:
http://www.heilancoo.net/MacCVSClient/MacCVSClientDoc/rbl-spec.htmlThis has worked really quite well in the MacCVSClient context. With it we were
able to merge resource files on a RESOURCE/INDEX basis. As good as it gets unless you have detailed knowledge of structure of the actual content of a resource.
So I wonder whether it is something you might find useful.
Cheers,
Joerg
On Wed, July 18, 2007 11:54 pm, Alastair Houghton <
alastair@...> said:
> On 18 Jul 2007, at 21:54, Gregory Gerard wrote:
>
>> What about adding a property per resource item? mac:rsrc-<hex
>> encoded resource type>-<hex encoded resource number>
>
> I wouldn't be inclined to use it that way, especially if (as you
> imply) these can go up to 16MB in size (which fits the description
> "very large", I think). It sounds like exactly the kind of thing
> that the authors of Subversion weren't expecting people to use
> properties for
>
> Probably the best thing to do would be to use AppleDouble (i.e. "._"
> files) for the resource fork, because that would also mean that if
> you checked code out on e.g. Linux or Windows, the resource forks
> would stay with the files.
>
> Of course, we also need to see if the Subversion people are doing any
> work on this front.
>
> Kind regards,
>
> Alastair.
>
> --
>
http://alastairs-place.net>
>
>
>
> _______________________________________________
> MacOSX-dev mailing list
>
MacOSX-dev@...
>
http://www.omnigroup.com/mailman/listinfo/macosx-dev>
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev
