in reply to When you change Perl versions, how do you resync all the CPAN modules you have installed [tag://sysadmin,cpan,modules,upgrade]

Then all sorts of things start breaking due to modules not being available.

That's not always true, although it depends on what version you're upgrade to/from. Standard Perl practice is to include in the @INC paths the paths from prior compatible versions.

If you do need to reinstall your modules then want to make a list of them and feed them to CPAN.pm. I'm sure someone has a clever one-liner for that, but I can cook something up for you if nobody does.

BTW, what's that tag:// junk at the end of your title?

-sam

  • Comment on Re: When you change Perl versions, how do you resync all the CPAN modules you have installed [tag://sysadmin,cpan,modules,upgrade]

Replies are listed 'Best First'.
Re^2: When you change Perl versions, how do you resync all the CPAN modules you have installed [tag://sysadmin,cpan,modules,upgrade]
by Corion (Patriarch) on Nov 13, 2007 at 21:29 UTC
    perl -MCPAN -e autobundle

    But I would never upgrade the system Perl without proper testing, and blindly upgrading a whole system sounds very fraught with errors to me. Compiling your own Perl is easy, even on Win32 nowadays, and there's no reason to use the system Perl when you're not installing modules using the packaging tool of the system as well. Under Debian, this means apt-get of course.