John Peacock wrote:
I have a couple of CPAN Testers failures listed against SVN::Notify::Config
specifically because I specified a minimum Module::Build release, and the person
running the tests upgraded Module::Build in the test sandbox, while trying to
build SVN::Notify::Config. I hate this, because it means I don't find out about
actual failures in my code, but rather only failures in the testing framework.
This isn't the testing framework's problem.
You are the one that specified a dependency to be fulfilled AFTER
Build.PL runs, which we already know will cause M:B to freak out.
The testing framework just did exactly what you said.
It may not be your line of code that failed, but it's still your
responsibility for breaking the toolchain in your Build.PL, and thus the
bug is correctly yours.
As a last alternative, perhaps the die() could be replaced with a prompt()
asking the user to decide whether to continue with allow_mb_mismatch in place
(with a default of Y). This would have the correct behavior under CPAN Testing
or CPANPLUS, in that a non-interactive install would throw a warning, but not
stop the installation.
This is the worst possible solution.
The user installing modules via CPAN cannot be assumed to a) Know Perl
b) Have any idea what the hell you are talking about.
Adam K
