I don't think that's true. Module::Build calls upon ExtUtils::Manifest to check the completeness of the MANIFEST in the "distcheck" action or to update the MANIFEST for the "manifest" action. That should use a MANIFEST.SKIP file, if one exists.

To the original poster, could you please give an example of what's in your MANIFEST.SKIP that isn't working and perhaps show some output from a "Build distcheck" action?

I did a bit more digging and I think I've found the issue. I'm doing mixed development. That is to say that I'm developing on both a Linux and a Windows machine. I had originally generated the MANIFEST.SKIP file on the Windows machine, but was seeing the above mentioned behavior on the Linux machine. For whatever reason, the light bulb flashed: line endings. I've confirmed that this is the case: running my MANIFEST.SKIP file through perl -i -ple 's/^M//' MANIFEST.SKIP and re-generating the MANIFEST gives the desired results. I think I'll send an e-mail to the Module::Build folks and see what they say. In the interim though, problem solved!

thor

The only easy day was yesterday

I have had a similar problem, as I use Subversion (well, really SVK) to shuttle files between my Linux and Windows machines. In Subversion, you need to set the svn:eol-style properties appropriately because it doesn't handle line ending conversions by default.

If that's what you're using, too, check out SubversionConfigurationForLineEndings for how to set up a config file to automatically do this for you.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

If you use Cygwin on Win32, then you won't have any problems with line-endings. I occasionally have to jump over and that's worked for me.

---

My criteria for good software:

1. Does it work?
2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?