The pip ("Perl Installation Program") console application is used to install Perl distributions in a wide variety of formats, both from CPAN and from external third-party locations, while supporting module dependencies that go across the boundary from third-party to CPAN.

Using pip you can install CPAN modules, arbitrary tarballs from both the local file-system or across the internet from arbitrary URIs.

You can use pip to ensure that specific versions of CPAN modules are installed instead of the most current version.

And beyond just single installations, you script script a series of these installations by creating a "P5I" (Perl 5 Installation) file.

A Perl 5 Installation (P5I) file is a small script-like file that describes a set of distributions to install, and integrates the installation of these distributions with the CPAN installer.

The primary use of P5I files are for installing proprietary or non-CPAN software that may still require the installation of a number of CPAN dependencies in order to function.

P5I files are also extensible, with the first line of the file specifying the name of the Perl class that implements the plan.

For the moment, the class described at the top of the P5I file must be installed.

The simple Module::Plan::Lite plan class is bundled with the main distribution, and additional types can be installed if needed.

Also on the development schedule for pip is the creation and installation of distributions via "P5Z" files, which are tarballs containing a P5I file, as well as all the distribution tarballs referenced by the P5I file.

It is also anticipated that pip will gain support for PAR binary packages and potentially also for ActivePerl PPM files.

Write access to the repository is made available automatically to any published CPAN author, and to most other volunteers on request.

If you are able to submit your bug report in the form of new (failing) unit tests, or can apply your fix directly instead of submitting a patch, you are strongly encouraged to do so. The author currently maintains over 100 modules and it may take some time to deal with non-Critical bug reports or patches.

This will guarentee that your issue will be addressed in the next release of the module.

If you cannot provide a direct test or fix, or don't have time to do so, then regular bug reports are still accepted and appreciated via the CPAN bug tracker.