In a presentation at the Second German Perl Workshop, Andreas König, author of CPAN, gave a talk on his module, mentioning explicitly that you are expected to manage the dependencies in a bundle file yourself. The autobundle feature is merely a convenience to get you started.

My advice would be to generate a snapshot with the autobundle feature, and then hand-tune it till you like it. Core modules should be avoided, since they will install a new perl (as brother Fastolfe pointed out). You can install core modules *without* installing a new perl by hand-fetching (or building) a distribution tarball for them, and installing that by a local script.

This trivial subroutine does a simple install from a distribution tarball under Linux/Unix:

sub install_perl_module {
    my ($tarball) = @_;
    my $dir = $tarball;
    $dir =~ s/\.tar\.gz//;

    my $cmd = 'tar -zxvf ' . $tarball . ' ; ' .
        'pushd ' . $dir . ' ; ' .
            'perl Makefile.PL ; make ; make test ; make install ; ' .
                'popd';
    system($cmd);
}
[download]

Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com

First, try shifting things around in the bundle list, to put some of the lower-level modules first before you get to the larger ones that use those modules.

Second, eliminate core modules from your bundle file. Things like IO::Socket are bundled *with* Perl, so if you're telling it to install it, it may be confused and try to install it separately by downloading the parent package that it's installed under (e.g perl_5.6).

Third, did you let it finish? Perhaps it is keeping track of dependencies and would have tried loading them after the bundle file had been exhausted? Bundle behavior seems to be inconsistent sometimes from what I've read.

One of the problems is that a bundle is supposed to be presented in a way that already gets dependencies straight. But once everything is installed it is hard to figure that out again.

Here's the sloppy way I attempt to save some time when in the same situation. This answer does not attempt to provide a resolution to the autobundle problems.

When you setup your cpan module on your 'base' system set it up with a huge cache (I set mine at 200 megs), also on the cache cleaning set it to 'never' I then setup my base perl on the clone system and just move the .cpan directory over. Install cpan.pm and let cpan.pm resovle the dependencies.

This is a serious cludge fix but it does save me time on a regular basis. There is a significant time saving in not having to dl all the bundles. I should also point out that more than half the time the bundles I have in the cache have been updated so there is still dl time involved.