For Module Authors working on Macs...

Matts on 2006-04-24T01:12:11

Remember this:

COPY_EXTENDED_ATTRIBUTES_DISABLE=1 make dist

Instead of the usual "make dist". Otherwise resource forks get included, and some versions of MakeMaker try and run ._Makefile.PL, and discover it has weird characters in it.

---

Using MANIFEST.SKIP

jonasbn on 2006-04-24T07:16:18

I currently just have the following lines in my MANIFEST.SKIP

# OSX files
\._

I use Module::Build for most of my stuff.

Re:Using MANIFEST.SKIP

Matts on 2006-04-24T12:53:32

That doesn't work. The resource forks still get included. The reason is that MANIFEST.SKIP just tells you how to build the MANIFEST file (when you run "make manifest"). So the MANIFEST file doesn't contain ._Makefile.PL, but it still gets included because when tar runs, and it sees Makefile.PL, it splits it into two files automatically - despite you not asking it for anything extra.

This ONLY happens if you've been editing those files in an editor that creates resource forks of course - I was using TextWrangler.

Double negative

hex on 2006-04-24T14:03:58

(Disclaimer: I have never developed Mac software. This is a passing snipe.)

"COPY_EXTENDED_ATTRIBUTES_DISABLE=1" seems a little backwards. Couldn't they (I don't know who that is... MakeMaker developers?) have named the flag simply "COPY_EXTENDED_ATTRIBUTES"?

Re:Double negative

AndyArmstrong on 2007-10-13T14:43:41

COPY_EXTENDED_ATTRIBUTES_DISABLE affects the behavior of Mac OS X tar - it has nothing directly to do with EUMM.