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=<Thank you for your attention.
CPAN.pm smokers
srezic on 2007-11-21T20:06:28
Smokers using CPAN.pm based systems may use a distribution preference file:---
match:
distribution: "/Perl-Dist-\d"
disabled: 1do not fight just the symptoms
jhi on 2007-11-21T22:42:55
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?
Re:do not fight just the symptoms
Alias on 2007-11-21T23:50:37
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...
Re:do not fight just the symptoms
jhi on 2007-11-22T02:05:39
> 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.
Re:do not fight just the symptoms
Alias on 2007-11-23T03:12:14
> 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 install pushing the files to the wrong place.
So Perl::Dist now overwrites and/or sanitizes all the environment variables used by the toolchain modules before it hands off to processes.
Re:do not fight just the symptoms
Alias on 2007-11-23T03:12:48
And in fact, at one point CPAN.pm, running make test, running CPAN.pm, running make test, running CPAN.pm, running make test:)
Perl::Dist current version has 100% PASS rate...
Alias on 2007-11-22T00:01:47
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.06Re:Perl::Dist current version has 100% PASS rate..
BinGOs on 2007-11-22T08:22:26
This is the last gasp of a dying man
After this Config.pm was gone. Perl::Dist was seen leaving the scene with a smoking gun >:)
