Re^3: Should I list core modules as dependencies?

[Khen1950fx]

If you look a little deeper at the long-tail of core modules, you'll see that most of the core modules listed are dual-lived. Those are the core modules that are costantly being updated and can be downloaded from CPAN. I usually avoid listing non-dual-lived modules because they will cause CPAN to try to install perl again, which isn't what you or the user really want. For example, if you try to install bytes---CPAN will install bytes but also all of the core all over again.

Let's look at the list you gave. I left out the non-dual-lived modules:

#!/usr/bin/perl

use strict;
use warnings;
use CPAN;

CPAN::Shell->install(qw(
    Carp
    Exporter
    File:Temp)
);

Adding the dependencies for Test::Deep:

#!/usr/bin/perl

use strict;
use warnings;
use CPAN;

CPAN::Shell->install(qw(
    Exporter
    Carp
    File::Temp
    Test::NoWarnings
    Test::Tester
    ExtUtils::MakeMaker
    Test::More
    List::Util)
);

Does that help? Just remember to list dual-lived dependencies. The non-dual-lived modules are already there, just waiting for you:).