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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
do not fight just the symptoms (Score:2)
Re: (Score:1)
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: (Score:2)
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 (Score:1)
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.
Reply to This
Parent
Re: (Score:1)