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.
In reply to Re: Perl::Minimal -- the good, bad, and the ugly...
by mr_mischief
in thread Perl::Minimal -- the good, bad, and the ugly...
by taint
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |