One of Perl’s cardinal strengths is the depth and variety of add-on modules to extend its capabilities, collected for the past 26 years and counting on CPAN, the Comprehensive Perl Archive Network. Starting with version 5.004 in 1997, Perl has come packaged with a module (also called CPAN) and associated command-line client for downloading and installing from this service. Some developers favor alternative tools such as CPANPLUS and its
cpanp command or cpanminus and its
cpanm, or tools built on the latter such as Carton and Carmel.
My favorite of these over the past several years has been Shoichi Kaji’s
cpm, mainly because it’s blazingly fast. As an example, the documentation cites an installation of Plack, the Perl web application toolkit, as taking three times as long using
cpm. Both use the same Menlo core code but
cpm achieves its speed by breaking down dependencies into individual streams, installing modules in parallel, and synchronizing the necessary worker processes.
It’s very important to note that
cpm is not a drop-in replacement for the
cpanm command-line tools. Firstly, it uses the subcommand
cpm install Module::Name. Also, by default, it installs modules into a subdirectory named
local/ as if you specified
cpanm --local-lib-contained local. You might want this if you’re setting up a Perl project with its non-core dependencies in a separate location addressed by the local::lib module; otherwise, you should use
cpm install --global to install into a directory in Perl’s
@INC array. I tend to do the latter when developing, declaring my project’s dependencies in a
cpm will use a
cpanfile to drive project dependency installation. In fact, it defaults to looking for one if you don’t specify individual modules on the command line and supports the version-controlled
cpanfile.snapshot file introduced by Carton for tracking exact dependencies used by your project. This is great for repeatedly building Docker containers and
cpm makes that process even faster.