Matts (email not shown publicly) I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
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.
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 TextWrang
(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"?
Using MANIFEST.SKIP (Score:2)
Re:Using MANIFEST.SKIP (Score:2)
This ONLY happens if you've been editing those files in an editor that creates resource forks of course - I was using TextWrang
Double negative (Score:1)
"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: (Score:1)