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

use Perl Log In

Log In

[ Create a new account ]

BinGOs (7246)

BinGOs
  (email not shown publicly)
http://gumbynet.org.uk/

System administrator, part-time Perl hacker, full-time POE [perl.org] evangelist. One day he will be made to pay for his crimes.

He has some modules on CPAN [cpan.org]. They may or may not be useful

Journal of BinGOs (7246)

Wednesday November 21, 2007
08:38 AM

Warning: CPAN smoking can damage your health

[ #34948 ]

Or rather smoking certain CPAN modules can damage your perl

Andreas König spotted it first, but I have had two smokers destroyed in the past two days by smoke testing Perl::Dist.

If you are using a CPANPLUS/CPAN::YACSmoke smoker I would advise excluding 'Perl-Dist' for the moment using a cpansmoke.ini file:

[CONFIG]
exclude_dists=<<HERE
^Perl-Dist
HERE

Thank you for your attention.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Warning: CPAN smoking can damage your health 8 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Smokers using CPAN.pm based systems may use a distribution preference file:

    ---
    match:
      distribution: "/Perl-Dist-\d"
    disabled: 1
  • Uh, shouldn't the author of Perl::Dist be firmly kicked in the backside until he removes the harmful distribution from CPAN and uploads a fixed version?

    • I'm the author of Perl::Dist, and I thought I HAD removed the destructive versions and uploaded fixed versions.

      Which leads us to the position of...

      How do you know your module is destructive to CPAN Testers until it is run by CPAN Testers?

      It works fine for me, I'm just not sure what the hell it's doing to them that is so different... most of the destructive tests skip now...
      • > How do you know your module is destructive to CPAN Testers until it is run by CPAN Testers?

        Become a CPAN tester and run your modules manually through the testing framework?

        > It works fine for me, I'm just not sure what the hell it's doing to them that is so different... most of the destructive tests skip now...

        I suggest working with Andreas König on figuring this one out.

        • > Become a CPAN tester and run your modules manually through the testing framework?

          My release automation does run modules through test runs in a couple of variations (with and without AUTOMATED_TESTING, etc) but it apparently didn't catch it.

          The problem turned out to be that you had CPAN.pm, running make test, running CPAN.pm, running make install (intentionally and correctly so)

          The top CPAN.pm did some funny business with PERL5LIB, which interacted in a complicated way and resulting in the bottom make i
          • And in fact, at one point CPAN.pm, running make test, running CPAN.pm, running make test, running CPAN.pm, running make test :)
  • I don't know if that means this is fixed already, or Perl::Dist will EITHER pass ok, or blow up the CPAN Testers setup...

    http://cpantesters.perl.org/show/Perl-Dist.html#Perl-Dist-0.06 [perl.org]
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.