Re: Should I list core modules as dependencies?

If your module supports older version of Perl, then there may be (probably are!) modules that were not in the Core List at that time.

At a minimum, I'd include as dependencies all of the modules that were not in the Core List for the earliest Perl version you support. I suspect that the Core List will only grow larger, since removing Modules from the Core would cause breakage, and the P5P tries hard to be backwardly compatible.

----
I Go Back to Sleep, Now.

OGB

Comment on Re: Should I list core modules as dependencies?

Replies are listed 'Best First'.
Re^2: Should I list core modules as dependencies? by tobyink (Canon) on Jun 02, 2013 at 07:36 UTC
"I suspect that the Core List will only grow larger" Modules are quite often moved out of core. Some of the biggies have been Class::ISA and Switch which were both removed in 5.14. CPANPLUS and Module::Pluggable are due to go in 5.20; and CGI and Module::Build will ~~probably~~ go in 5.22. Update: removed "probably"; it's now official; they're going. `package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name`	[reply]

Replies are listed 'Best First'.

Re^2: Should I list core modules as dependencies?
by tobyink (Canon) on Jun 02, 2013 at 07:36 UTC

"I suspect that the Core List will only grow larger"

Modules are quite often moved out of core. Some of the biggies have been Class::ISA and Switch which were both removed in 5.14.

CPANPLUS and Module::Pluggable are due to go in 5.20; and CGI and Module::Build will ~~probably~~ go in 5.22.

Update: removed "probably"; it's now official; they're going.

package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name

[reply]