Re^2: upgrade of B::C failure

Replies are listed 'Best First'.
Re^3: upgrade of B::C failure by Anonymous Monk on Aug 06, 2010 at 01:53 UTC
I would feel uncomfortable forcing an installation while there are test errors. Why? What is a few test failures when THIS CODE IS HIGHLY EXPERIMENTAL. USE AT YOUR OWN RISK.?	[reply]
Re^4: upgrade of B::C failure by dnessett (Initiate) on Aug 06, 2010 at 21:03 UTC
Not sure what happened. My last post didn't show up (an empty slot for it did though - which is kind of strange). So, I will repeat my comments. Unless there is some way of excluding modules from ugrading when executing the upgrade command, I can't just ignore the B::C problem. I have set halt_on_failure so any installs I make don't continue if a dependent module fails to build. So, I can't complete the upgrade until I figure out how to get past the B::C upgrade problem	[reply]
Re^4: upgrade of B::C failure by dnessett (Initiate) on Aug 06, 2010 at 15:28 UTC
Perhaps I am unaware of a way to exclude specific modules from upgrading when running upgrade from the interactive cpan command line. If there is a way to do this, let me know. Otherwise, unless I set halt_on_failure to no (which allows the global upgrade to continue even if some module upgrades fail), then I can't complete the global upgrade. Setting halt_on_failure to no means when I do an install, failed dependencies will not halt the install, which is not what I want to happen.	[reply]