Re^2: Module make problems caused by Mac OS metadata files

I think my MANIFEST file is working. The only files that end up in the archive are the files specified in MANIFEST, plus their metadata. Interestingly, these metadata files do not really exist before making the archive, they are somehow created in the process:

$ ls -la | grep Makefile.PL
-rw-r--r--   1 planz  planz  577 Jun 15 18:53 Makefile.PL

$ tar cf test.tar Makefile.PL

$ tar tf test.tar 
./._Makefile.PL
Makefile.PL
[download]

So, I think if I want to stop having these metadata files in the archive, I need to pass some Mac-specific flag to the tar program. But tar --help did not reveal anything useful (just the regular GNU tar description).

My current work-around is to make the bundle on a Linux machine. Using a pre-Tiger OS X should also work, as the metadata-preservation seems to be a new feature.

Comment on Re^2: Module make problems caused by Mac OS metadata files Download Code

Replies are listed 'Best First'.
Re^3: Module make problems caused by Mac OS metadata files by davidrw (Prior) on Jun 18, 2005 at 03:30 UTC
hmm.. no flag, eh? could it be as simple as just removing (note: i didn't test my --delete syntax) the files from the archive? was does this show as the list? `tar cvf test.tar Makefile.PL tar --delete -vf test.tar ._Makefile.PL # any error?? tar tf test.tar # is it still there?` [download]	[reply] [d/l]
Re^4: Module make problems caused by Mac OS metadata files by Thilosophy (Curate) on Jun 18, 2005 at 03:54 UTC
Thanks, that works. So my improved workaround now becomes to "clean" the tar file before shipping it.	[reply]