in reply to
Re^2: Should I list core modules as dependencies?
in thread Should I list core modules as dependencies?
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
Adding the dependencies for Test::Deep:
Does that help? Just remember to list dual-lived dependencies. The non-dual-lived modules are already there,
just waiting for you:).