Like many programming languages, Perl has mechanisms to use external libraries of code, making one file contain common routines used by several programs. Perl modules are typically installed in one of several directories whose paths are placed in the Perl interpreter when it is first compiled; on Unix-like operating systems, common paths include /usr/lib/perl5, /usr/local/lib/perl5, and several of their subdirectories. Some of these perform bootstrapping tasks, such as , which is used for building and installing other extension modules; others, like CGI.pm, are merely commonly used. Forking, and creating competing modules for the same task or purpose is common.
The CPAN's main purpose is to help programmers locate modules and programs not included in the Perl standard distribution. There is no formal bug tracking system, but there is a third-party bug tracking system that CPAN designated as the suggested official method of reporting issues with modules.
Continuous development on modules is rare; many are abandoned by their authors, or go years between new versions being released.
Search by name, author, or keywords in the description.
In addition to the modules already bundled with Active Perl, there are thousands more Perl modules that can be installed from PPM - the Active Perl online repository of compiled CPAN distributions.
However, note that binary modules installed this way may seemingly inexplicably break after upgrading to a newer Fedora release.
Most modules include test scripts, which you should run to ensure that the module has been built correctly: Can't locate Data/in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at -e line 1.
If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.