Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Adam,

    I think you make a good case for getting rid of these files.

          Makr
    • Oops. It's just only too bad I didn't notice I spelled my own name wrong before I hit Submit...
  • Of course the real mechanism to verify signatures is out of band. The command that does it is cpansign -v. The 00-signature.t file simply does the equivalent of cpansign -v to verify that it actually works.

    Just like tests generally just verify that something does what it intends to do.

    Imagine that an author signs his work wrongly. During make disttest he will notice the bug and has a chance to fix the thing before releasing. Just like with any other test.

    • In which case never, under any circumstances, should this test EVER run during installation.

      It should be a compulsory skip, unless something like AUTOMATED_TESTING of AUTHOR_TESTING is enabled.
      • Correct. It was intended as a convenience measure for "make disttest", that's all.

        The standard boilerplate 0-signature.t (as documented in Module::Signature's POD) has this opening:

        if (!$ENV{TEST_SIGNATURE}) {
            print "ok 1 # skip set the environment variable TEST_SIGNATURE to enable this test\n";
        }
        Which satisfies the compulsory skip requirement via the environment variable TEST_SIGNATURE.
        • Do you think it's necessary to have its own TEST_SIGNATURE flag?

          If the contexts in which it should be used are clear, perhaps it would be better to flag in on AUTOMATED_TESTING or a context-appropriate flag.
  • I write you this way because mail seems to fail and your post on my blog is to old that a reply would be noticed by you.

    First thanks for attention. I really push it now for CPAN release but please notice that i have a little different viewpoint on some things.

    I really admire you skills to carry out loads of modules in high quality but please trust me GUI-User apps are different territory. I impeled myself the last 2 month and did nearly every day a nightly release. i cleaned up shitloads of nasty details an
    • Module::Signature is not necessary to release to CPAN.
      • im not that experienced but P6bible has a signature file. to generate the new sigs i thought i need Module::Sig.
        • It's not strictly needed for you to release with a signature file, even if Audrey does.

          This is especially so if you are in Windows, as the support for Module::Signature on Win32 is weak.