# with arguments and no switches, installs specified modules
               cpan module_name [ module_name ... ]

               # with switches, installs modules with extra behavior
               cpan [-cfgimtTw] module_name [ module_name ... ]

               # with just the dot, install from the distribution in the
               # current directory
               cpan .

               # without arguments, starts shell

               # dump the configuration
               cpan -J

               # load a different configuration to install Module::Foo
               cpan -j some/other/file Module::Foo

               # without arguments, but some switches
               cpan [-ahrvACDlLO]

       This script provides a command interface (not a shell) to CPAN. At the
       moment it uses to do the work, but it is not a one-shot command
       runner for

       -a  Creates a autobundle with CPAN::Shell->autobundle.

       -A module [ module ... ]
           Shows the primary maintainers for the specified modules.

       -c module
           Runs a `make clean` in the specified module's directories.

       -C module [ module ... ]
           Show the Changes files for the specified modules

       -D module [ module ... ]
           Show the module details.

       -f  Force the specified action, when it normally would have failed. Use
           this to install a module even if its tests fail. When you use this
           option, -i is not optional for installing a module when you need to
           force it:

                   % cpan -f -i Module::Foo

       -F  Turn off's attempts to lock anything. You should be careful
           with this since you might end up with multiple scripts trying to
           muck in the same directory. This isn't so much of a concern if
           each distribution.

           If you want this feature, check out Yanick Champoux's
           "Git::CPAN::Patch" distribution.

       -h  Print a help message and exit. When you specify "-h", it ignores
           all of the other options and arguments.

       -i  Install the specified modules.

       -I  Load "local::lib" (think like "-I" for loading lib paths).

           Load the file that has the CPAN configuration data. This should
           have the same format as the standard CPAN/ file, which
           defines $CPAN::Config as an anonymous hash.

       -J  Dump the configuration in the same format that uses. This
           is useful for checking the configuration as well as using the dump
           as a starting point for a new, custom configuration.

       -l  List all installed modules wth their versions

       -L author [ author ... ]
           List the modules by the specified authors.

       -m  Make the specified modules.

       -O  Show the out-of-date modules.

       -p  Ping the configured mirrors

       -P  Find the best mirrors you could be using (but doesn't configure
           them just yet)

       -r  Recompiles dynamically loaded modules with CPAN::Shell->recompile.

       -t  Run a `make test` on the specified modules.

       -T  Do not test modules. Simply install them.

       -u  Upgrade all installed modules. Blindly doing this can really break
           things, so keep a backup.

       -v  Print the script version and version then exit.

       -V  Print detailed information about the cpan client.


           Turn on cpan warnings. This checks various things, like directory
           permissions, and tells you about problems you might have.

               # upgrade all installed modules
               cpan -u

               # install modules ( sole -i is optional )
               cpan -i Netscape::Booksmarks Business::ISBN

               # force install modules ( must use -i )
               cpan -fi CGI::Minimal URI

           "cpan" splits this variable on whitespace and prepends that list to
           @ARGV before it processes the command-line arguments. For instance,
           if you always want to use "local:lib", you can set "CPAN_OPTS" to

       The script exits with zero if it thinks that everything worked, or a
       positive number if it thinks that something failed. Note, however, that
       in some cases it has to divine a failure by the output of things it
       does not control. For now, the exit codes are vague:

               1       An unknown error

               2       The was an external problem

               4       There was an internal problem with the script

               8       A module failed to install

       * one shot configuration values from the command line

       * none noted

       Most behaviour, including environment variables and configuration,
       comes directly from

       This code is in Github:


       Japheth Cleaver added the bits to allow a forced install (-f).

       Jim Brandt suggest and provided the initial implementation for the up-
       to-date and Changes features.

       Adam Kennedy pointed out that exit() causes problems on Windows where
       this script ends up with a .bat extension
Man Pages Copyright Respective Owners. Site Copyright (C) 1994 - 2018 Hurricane Electric. All Rights Reserved.