This isn't a good piece of advice. Without knowing the reason of the failure, this can break modules that worked previously. Moreover, newbies usually don't backup their PERL5LIB before the installation, so there might be no easy way back.
Prove it? Disengage pedantic autopilot and look up, those aren't trees, thats a forest!
Newbies aren't aware you can install modules with failing tests, or skip testing altogether -- an option that is always available to test
Skip the tests or force the install and install the modules today now with no waiting
Then see if that breaks anything in your existing codebase
See if firefox mechanize will work now
IPC::Run is pure-perl, easy to install, uninstall, reinstall, revert ... backup not required
Look at the failing test, the single solitary failing test ... trying to close an already destroyed filehandle ... thats nothing to worry about ... and certainly nothing for any kind of non author to fuss about
Also look at the documentation, esp the caveats for windows
Bad advice? No thats just uninformed criticism
In reply to Re^3: WWW-Mechanize-Firefox install issue
by Anonymous Monk
in thread WWW-Mechanize-Firefox install issue
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |