Specifically, Leopard's tar command. Now it, when you are creating good old .tar.gz archive, will also try to slip into it a bunch of files with names like ._.foo.xml, if your archive to contain foo.xml file.
Wisdom of internets (Leopard's tar is broken, OSX considered harmful) pointed to the solution:
export COPYFILE_DISABLE=yIt's going straight into my
~/.profile.Isn't this the traditional resource fork metadata for OS X?
From a Mac user's point of view, this could be argued as safer behaviour than the earlier versions of traditional UNIX utilities, which of course access data forks only - silently stripping resource forks.
Then again, Mac users should be using a properly Mac-metadata aware application for archiving (StuffIt) and not tar... So in sum, I see your point. :)
Posted by: Toby at January 8, 2008 12:19 PMYep, you got it right :) When you use tar to prepare a release of something, you certainly do not mean to include those resource forks.
Posted by: Vadim at January 8, 2008 1:12 PM