You can create a bundle of all installed modules by using the autobundle command from the CPAN.pm shell. On your fresh Perl installation, you then just install that bundle and it will pull down all modules and try to install them. cbrandtbuffalo wrote Order your autobundle by dependency, which can make the installation of your bundle more convenient.

That concept does not extend well to Perl modules that require external libraries, like libxml or ImageMagic, but there is no common way to install and configure external libraries anyway.

5.8.3 is binary compatible with 5.8.0, which in general is true if only the subversion (the 3rd part of the number) differs.

So instead of downloading and recompiling all your modules, simply configure the new Perl to include the existing module directories in @INC.

Smylers

Perhaps in the general case, but Abigail's answer in this thread seems to indicate that 5.8.3 and 5.8.0 are not binary compatible (unless they rolled back the change they made in 5.8.1)

perl582delta

Incompatible Changes
    For threaded builds for modules calling certain re-entrant system calls,
    binary compatibility was accidentally lost between 5.8.0 and 5.8.1.
    Binary compatibility with 5.8.0 has been restored in 5.8.2, which
    necessitates breaking compatibility with 5.8.1. We see this as the
    lesser of two evils.

    This will only affect people who have a threaded perl 5.8.1, and
    compiled modules which use these calls, and now attempt to run the
    compiled modules with 5.8.2. The fix is to re-compile and re-install the
    modules using 5.8.2.