in reply to Perl::Minimal -- the good, bad, and the ugly...

A minimal Perl core is considered by many to have what's needed to run CPAN and the cpan script. One could try to figure out the requirements of that.

A really bare-bones Perl only needs what is necessary for the core pragmas, handling of @INC, DynaLoader for XS, ExtUtils::MakeMaker, and so forth. If you don't mind losing the functionality of CPAN.pm you can do away with a few more modules.

Then there's miniperl which doesn't even handle dynamic loading for XS, but which can convert XS to C to be compiled and linked into perl. I'd call miniperl just a bit less than barebones Perl. It's used in the build process of the perl executable. Looking at the compilation or even cross-compilation process to build perl could be a good way to determine which modules are really needed to get to a certain point you consider complete.

Replies are listed 'Best First'.
Re^2: Perl::Minimal -- the good, bad, and the ugly...
by taint (Chaplain) on May 30, 2014 at 18:12 UTC
    Hello, mr_mischief.

    Looking at minimod.PL. It appears to provide much, if not all, that's needed to write out a desired Minimal::Perl/Perl::Minimal/{<chosen-namespace-here>}. Indeed, it might also provide some clues for determining what should/would be considered the optimal/ideal Perl::Minimal.

    Thanks for pointing it out, mr_mischief.

    --Chris

    ¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH