I'm assuming you're still working in an environment that uses the customer's OS version of Perl.
For our (large) product, I insisted we build and bundle our own Perl (along with a carefully selected set of stable, well-respected CPAN modules). Had I been ordered instead to use the system Perl, I'd have used Perl only for smallish Unix shell scripts - and, like you, would've avoided non-core CPAN modules like the plague. That is, we'd probably have written all of our large complex components in C++, not Perl.
I might add that in our bundled Perl, we only bundled large, solid CPAN modules, like DBI, not small convenience modules, like File::Slurp. I'm happy to avoid the dependency cost by rolling my own file slurper, less keen to roll my own DBI. :)
See also the "Dependencies" section at Writing Solid CPAN Modules.
Update: As an aside, I stumbled upon RFC: Private CPAN In A Box by Perl::Critic creator jthalhammer (where he relates his experiences building private CPANs, aka Darkpans, for customers; RPM Package Manager was also mentioned).
In reply to Re: Prefer Pure Perl Core Modules
by eyepopslikeamosquito
in thread Prefer Pure Perl Core Modules
by Leitz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |