http://qs321.pair.com?node_id=734797

jaldhar has asked for the wisdom of the Perl Monks concerning the following question:

I have problems getting a module I wrote to build properly under Windows. I use Module::Signature to sign the module via sign => 1 in a Build.PL that uses Module::Build. A tester using strawberry perl 5.10.0 on Windows XP is reporting this...

./Build: blib\lib\Module\Starter\Plugin\CGIApp\templates\titanium \Module.pm: cannot resolve L<Titanium> in paragraph 48. JALDHAR/Module-Starter-Plugin-CGIApp-0.07.tar.gz C:\strawberry\perl\bin\perl.exe ./Build -- OK Running Build test t\00-signature............WARNING: This key is not certified with a trusted signature! Primary key fingerprint: A348 B1C3 F241 0234 14F8 30EF 20DF 5E33 A91F 8EBA Not in MANIFEST: Build.bat Not in MANIFEST: pod2htmd.tmp Not in MANIFEST: pod2htmi.tmp ==> MISMATCHED content between MANIFEST and distribution files! <== t\00-signature............1/1 # Failed test 'Valid signature' # at t\00-signature.t line 21. # Looks like you failed 1 test of 1. t\00-signature............ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests
...which makes sense as Build.bat and the *.tmp files are indeed not in the MANIFEST. They are created during the build process on Windows only. Do I just add them to MANIFEST.SKIP? Are there any possible other files I should be adding there? Or should the problem be solved an entirely different way?

--
જલધર

Replies are listed 'Best First'.
Re: Proper way to use Module::Signature under windows?
by andreas1234567 (Vicar) on Jan 08, 2009 at 08:48 UTC
    I would take the default MANIFEST.SKIP from Module::Build and modify it slightly if I were you.

    Also, you may try to contact the CPAN tester in question directly (or ask in the chatterbox for volunteers) to help you test on the given platform, or simply release a new version of our module and wait for the test reports to come in.

    Update: By adding

    \.tmp ^Build.bat$
    to your MANIFEST.SKIP I figure you could resolve the issue. But I cannot, of course, properly sign your module and verify that all tests actually pass.