[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Pre/Post-processing files on check-in/out

From: Steve Sisak <sgs_at_codewell.com>
Date: 2007-10-03 05:38:20 CEST

At 7:50 PM -0700 10/2/07, Jack Repenning wrote:
>>The MIME types for Mac OS file encodings have
>>been set in stone for at least a decade (maybe
>>2).
>>
>>Matt has proposed file:appledouble for the
>>property which contains the AppleDouble header
>>file (associate with a given data file) -- the
>>format of the contents has been defined since
>>A/UX. Unless there are major objections from
>>someone, it's fine with me.
>
>Why isn't the standard name for this property "svn:mime-type"?

Because AppleDouble encoding can be applied to _any_ MIME type.

>I think there are official standard MIME types
>for AppleDouble and -Single
>(multipart/appledouble and
>application/applefile, respectively), so
>anything with that MIME type could, by a Mac
>client, be exploded into the "real" file on
>checkout, and glommed back up on checkin, right?

Right -- I mentioned this, and the relevant MIME types in my original post.

The the encodings that result in a single file (a
binary blob) to other platforms have MIME types
and would use svn:mime-type.

AppleDouble encoding is used when the data fork
is useful to, and might be modified on other
platforms, so it would have it's own MIME type,
orthogonal to the AppleDouble encoding but might
still have Mac-specific metadata.

This is the rasion d'Ítre for AppleDouble. In
this case the date file (data fork) contains the
"normal" file and the header file contains the
Mac-specific data.

>(Mental note about non-Macophilic file systems,
>like UFS, on Mac platforms....)

These use AppleDouble -- the "._" file is the
header file, containing the Mac-specific data,
not the resource fork as is often bandied about
by people who are unfamiliar with the spec.

   <http://users.phg-online.de/tk/netatalk/doc/Apple/v1/>

An AppleDouble file does not necessarily need to
have a resource fork -- the header file still
preserves:

   Real Name
   Finder Comment
   Icons
   Creation Date
   Modification Date
   Last Backup Date
   Attributes
   Finder Info

Note that AppleSingle and AppleDouble are the
same format -- they differ in wether the data
fork is stored in a separate file or not,

Matt's solution is to store the AppleDouble
header file as a property of the data file (which
might have its own MIME type) -- therefore a
different property is needed.

Make sense?

-Steve

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 3 05:38:31 2007

This is an archived mail posted to the Subversion Dev mailing list.