Re: Standard OS X Compression format
Re: Standard OS X Compression format
- Subject: Re: Standard OS X Compression format
- From: Marcel Weiher <email@hidden>
- Date: Sat, 17 Nov 2001 16:00:54 +0100
On Saturday, November 17, 2001, at 03:52 PM, Ondra Cada wrote:
Marcel Weiher (MW) wrote at Sat, 17 Nov 2001 12:12:44 +0100:
MW> This is essentially what the hfstar patch to gnutar does: for each
MW> <plain-file> archived, also archive '<plain-file>/rsrc'. Nothing
MW> special needs to be done when untarring, it just works.
I don't think so.
What you think doesn't really matter in this case: it *does* just work.
As I have recommended ages ago, I think it would be much
better to move those resource forks into a separate tree, rooted (using
some
*QUITE* distinctive name) in /tmp.
"QUITE" distinctive names aren't good enough, because sooner or later,
someone is going to stumble across that name. Also, I don't see how
going to /tmp/ helps. As a matter of fact, I see going to /tmp/ as
rather problematic. What if /tmp/ is a different filesystem?
When unarchiving to HFS, the "macgnutar"
would catch this special name and restore resource forks.
The reason is simple -- to make the archive easily and without confusion
useable worldwide. Should you try to unpack archive of your design on,
say,
Linux, you'll get a pretty mess.
Not true. You will get warnings from tar but the resource forks will
simply not be untarred.
I have actually implemented this and tried it.
OTOH, should you unpack there "mine", you'll
get only some trash in /tmp, where it does not matter,
I think no trash whatsoever and warnings on the console are a better
solution.
Marcel
--
Marcel Weiher Metaobject Software Technologies
email@hidden www.metaobject.com
Metaprogramming for the Graphic Arts. HOM, IDEAs, MetaAd etc.