NAME

CPAN - query, download and build perl modules from CPAN sites

SYNOPSIS

Interactive mode:

perl -MCPAN -e shell;

Batch mode:

use CPAN;

bundle, bundles, expand, install, make, test

DESCRIPTION

The CPAN module is designed to automate the fetching and, optionally, the building and installing of perl modules and extensions.

Modules are fetched from one or more of the mirrored CPAN (Comprehensive Perl Archive Network) sites and unpacked in a dedicated directory.

The CPAN module also supports the concept of named and versioned 'bundles' of modules. Bundles simplify the handling of sets of related modules. See BUNDLES below.

INTERACTIVE MODE

The interactive more is entered by running

perl -MCPAN -e shell

which puts you into a readline interface. You will have most fun if you install Term::ReadKey and Term::ReadLine soon. That will give you both history and completion.

Once you're on the command line, type 'h' and the rest should be self-explanatory.

PREREQUISITES

If you have a local mirror of CPAN and can access all files with "file:" URLs, then you only need perl5.003 to run this module. Otherwise you need Net::FTP intalled. LWP may be required for non-UNIX systems.

This module presumes that all packages on CPAN

• Declare their $VERSION variable in an easy to parse manner. This prerequisite can hardly be relaxed because it consumes by far too much memory to load all packages into a single program just to determine the $VERSION variable . Currently all programs that are dealing with VERSION use something like this (requires MakeMaker-5.38, but don't bother if you don't have it):

  perl -MExtUtils::MakeMaker -le \
      'print MM->parse_version($ARGV[0])' filename

  If you are author of a package and wonder if your VERSION can be parsed, please try the above method.

• come as compressed or gzipped tarfiles or as zip files,

BUNDLES

A bundle is just a perl module in the namespace Bundle:: that does not define any functions or methods. It usually only contains documentation.

It starts like a perl module with a package declaration and a $VERSION variable. After that the pod section looks like any other pod with the only difference, that one pod section exists starting with (verbatim):

=head1 CONTENTS

In this pod section each line obeys the format

Module_Name [Version_String] [- optional text]

The only required part is the first field, the name of a module (eg. Foo::Bar, ie. not the name of the distribution file). The rest of the line is optional. The comment part is delimited by a dash just as in the man page header.

The distribution of a bundle should follow the same convention as other distributions. The bundle() function in the CPAN module simply parses the module that defines the bundle and returns the module names that are listed in the described CONTENTS section.

Bundles are treated specially in the CPAN package. If you say 'install Bundle::Tkkit' (assuming such a bundle exists), CPAN will install all the modules in the CONTENTS section of the pod. See the Bundle::PleaseIgnore on CPAN. I wrote it as a blueprint for other bundles. You can install your own Bundles locally by placing a placing a conformant Bundle file somewhere into your @INC path.

CONFIGURATION

When the CPAN module is installed a site wide configuration file is created as CPAN/Config.pm. The default values defined there can be overridden in another configuration file: CPAN/MyConfig.pm. You can store this file in $HOME/.cpan/CPAN/MyConfig.pm if you want, because $HOME/.cpan is added to the search path of the CPAN module before the use() or require() statements.

Currently the following keys in the hash reference $CPAN::Config are defined:

build_cache       size of cache for directories to build modules
build_dir         locally accessible directory to build modules
cache_expire      after how many days refetch index files
cpan_home         local directory reserved for this package
gzip		    location of external program gzip
keep_source       keep the source in a local directory?
keep_source_where where keep the source (if we do)
make              location of external program make
make_arg	    arguments that should always be passed to 'make'
make_install_arg  same as make_arg for 'make install'
makepl_arg	    arguments passed to 'perl Makefile.PL'
more              location of external program more (or any pager)
tar               location of external program tar
unzip             location of external program unzip
urllist	    arrayref to nearby CPAN sites (or equivalent locations)

SECURITY

There's no security layer in the alpha version of CPAN.pm. CPAN.pm helps you to install foreign, unmasked, unsigned code on your machine. It's not different than when you do that on your own, but you should be warned now.

EXPORT

All functions in package CPAN are exported. The reason for this is that the primary use is intended for the cpan-shell or for one-liners.

BUGS

Memory consumption is too high.

Not really a bug, but worth to mention: CPAN doesn't check if a module that is available in the path can really be require()d cleanly. Instead the module is parsed and the $VERSION variable is evaluated. Once that is done, the parsing stops and no further actions are taken. The reason for this is, that big bundles would cause a huge memory consumption just to check for the version.

AUTHOR

Andreas König <a.koenig@mind.de>

SEE ALSO

perl(1)

cpanm CPAN

perl -MCPAN -e shell
install CPAN