Now to your more general question: I would never let the cpan client upgrade perl under my feet.
If you upgrade a single module it will usually test itself fairly well, so you can be confident at least it works. You don't know if anything that depends on it, that was already installed, will keep working. Unless you run their tests as well, which will make it a lot more likely to show that those modules keep working. You cannot be sure if your application using this module will keep running correctly. Running the tests of your applications - you do have lots of unit and acceptance tests don't you? - might be able to show if something got broken by the upgrade or if things seem to be ok. Upgrading perl have the same effect many more fold. You can't be sure that anything that relies on it will keep working. Running the tests of those things will help reducing the risk. With that said, in well written code usually few things break. Theoretically you should be able to upgrade perl between minor versions (e.g. 5.18.0 to 5.18.2) and everything, including the binary compiled modules should keep working. In practice, I would not rely on this, and I'd reinstall and test the whole stack. regards Gabor _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
