Current Path : /proc/2/root/usr/share/man/man3/

Upload File :

Current File : //proc/2/root/usr/share/man/man3/CPAN::FirstTime.3pm

.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.13)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.el \{\
.    de IX
..
.\}
.\" ========================================================================
.\"
.IX Title "CPAN::FirstTime 3"
.TH CPAN::FirstTime 3 "2019-06-30" "perl v5.10.1" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
CPAN::FirstTime \- Utility for CPAN::Config file Initialization
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
\&\fICPAN::FirstTime::init()\fR
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
The init routine asks a few questions and writes a CPAN/Config.pm or
CPAN/MyConfig.pm file (depending on what it is currently using).
.PP
In the following all questions and explanations regarding config
variables are collected.
.IP "allow_installing_module_downgrades" 2
.IX Item "allow_installing_module_downgrades"
The \s-1CPAN\s0 shell can watch the \f(CW\*(C`blib/\*(C'\fR directories that are built up
before running \f(CW\*(C`make test\*(C'\fR to determine whether the current
distribution will end up with modules being overwritten with decreasing module version numbers. It
can then let the build of this distro fail when it discovers a
downgrade.
.Sp
Do you want to allow installing distros with decreasing module
versions compared to what you have installed (yes, no, ask/yes,
ask/no)?
.IP "allow_installing_outdated_dists" 2
.IX Item "allow_installing_outdated_dists"
The \s-1CPAN\s0 shell can watch the \f(CW\*(C`blib/\*(C'\fR directories that are built up
before running \f(CW\*(C`make test\*(C'\fR to determine whether the current
distribution contains modules that are indexed with a distro with a
higher distro-version number than the current one. It can
then let the build of this distro fail when it would not represent the
most up-to-date version of the distro.
.Sp
Note: choosing anyhing but 'yes' for this option will need
Devel::DistnameInfo being installed for taking effect.
.Sp
Do you want to allow installing distros that are not indexed as the
highest distro-version for all contained modules (yes, no, ask/yes,
ask/no)?
.IP "auto_commit" 2
.IX Item "auto_commit"
Normally \s-1CPAN\s0.pm keeps config variables in memory and changes need to
be saved in a separate 'o conf commit' command to make them permanent
between sessions. If you set the 'auto_commit' option to true, changes
to a config variable are always automatically committed to disk.
.Sp
Always commit changes to config variables to disk?
.IP "build_cache" 2
.IX Item "build_cache"
\&\s-1CPAN\s0.pm can limit the size of the disk area for keeping the build
directories with all the intermediate files.
.Sp
Cache size for build directory (in \s-1MB\s0)?
.IP "build_dir" 2
.IX Item "build_dir"
Directory where the build process takes place?
.IP "build_dir_reuse" 2
.IX Item "build_dir_reuse"
Until version 1.88 \s-1CPAN\s0.pm never trusted the contents of the build_dir
directory between sessions. Since 1.88_58 \s-1CPAN\s0.pm has a YAML-based
mechanism that makes it possible to share the contents of the
build_dir/ directory between different sessions with the same version
of perl. People who prefer to test things several days before
installing will like this feature because it saves a lot of time.
.Sp
If you say yes to the following question, \s-1CPAN\s0 will try to store
enough information about the build process so that it can pick up in
future sessions at the same state of affairs as it left a previous
session.
.Sp
Store and re-use state information about distributions between
\&\s-1CPAN\s0.pm sessions?
.IP "build_requires_install_policy" 2
.IX Item "build_requires_install_policy"
When a module declares another one as a 'build_requires' prerequisite
this means that the other module is only needed for building or
testing the module but need not be installed permanently. In this case
you may wish to install that other module nonetheless or just keep it
in the 'build_dir' directory to have it available only temporarily.
Installing saves time on future installations but makes the perl
installation bigger.
.Sp
You can choose if you want to always install (yes), never install (no)
or be always asked. In the latter case you can set the default answer
for the question to yes (ask/yes) or no (ask/no).
.Sp
Policy on installing 'build_requires' modules (yes, no, ask/yes,
ask/no)?
.IP "cache_metadata" 2
.IX Item "cache_metadata"
To considerably speed up the initial \s-1CPAN\s0 shell startup, it is
possible to use Storable to create a cache of metadata. If Storable is
not available, the normal index mechanism will be used.
.Sp
Note: this mechanism is not used when use_sqlite is on and SQLLite is
running.
.Sp
Cache metadata (yes/no)?
.IP "check_sigs" 2
.IX Item "check_sigs"
\&\s-1CPAN\s0 packages can be digitally signed by authors and thus verified
with the security provided by strong cryptography. The exact mechanism
is defined in the Module::Signature module. While this is generally
considered a good thing, it is not always convenient to the end user
to install modules that are signed incorrectly or where the key of the
author is not available or where some prerequisite for
Module::Signature has a bug and so on.
.Sp
With the check_sigs parameter you can turn signature checking on and
off. The default is off for now because the whole tool chain for the
functionality is not yet considered mature by some. The author of
\&\s-1CPAN\s0.pm would recommend setting it to true most of the time and
turning it off only if it turns out to be annoying.
.Sp
Note that if you do not have Module::Signature installed, no signature
checks will be performed at all.
.Sp
Always try to check and verify signatures if a \s-1SIGNATURE\s0 file is in
the package and Module::Signature is installed (yes/no)?
.IP "cleanup_after_install" 2
.IX Item "cleanup_after_install"
Users who install modules and do not intend to look back, can free
occupied disk space quickly by letting \s-1CPAN\s0.pm cleanup each build
directory immediately after a successful install.
.Sp
Remove build directory after a successful install? (yes/no)?
.IP "colorize_output" 2
.IX Item "colorize_output"
When you have Term::ANSIColor installed, you can turn on colorized
output to have some visual differences between normal \s-1CPAN\s0.pm output,
warnings, debugging output, and the output of the modules being
installed. Set your favorite colors after some experimenting with the
Term::ANSIColor module.
.Sp
Please note that on Windows platforms colorized output also requires
the Win32::Console::ANSI module.
.Sp
Do you want to turn on colored output?
.IP "colorize_print" 2
.IX Item "colorize_print"
Color for normal output?
.IP "colorize_warn" 2
.IX Item "colorize_warn"
Color for warnings?
.IP "colorize_debug" 2
.IX Item "colorize_debug"
Color for debugging messages?
.IP "commandnumber_in_prompt" 2
.IX Item "commandnumber_in_prompt"
The prompt of the cpan shell can contain the current command number
for easier tracking of the session or be a plain string.
.Sp
Do you want the command number in the prompt (yes/no)?
.IP "connect_to_internet_ok" 2
.IX Item "connect_to_internet_ok"
If you have never defined your own \f(CW\*(C`urllist\*(C'\fR in your configuration
then \f(CW\*(C`CPAN.pm\*(C'\fR will be hesitant to use the built in default sites for
downloading. It will ask you once per session if a connection to the
internet is \s-1OK\s0 and only if you say yes, it will try to connect. But to
avoid this question, you can choose your favorite download sites once
and get away with it. Or, if you have no favorite download sites
answer yes to the following question.
.Sp
If no urllist has been chosen yet, would you prefer \s-1CPAN\s0.pm to connect
to the built-in default sites without asking? (yes/no)?
.IP "ftp_passive" 2
.IX Item "ftp_passive"
Shall we always set the \s-1FTP_PASSIVE\s0 environment variable when dealing
with ftp download (yes/no)?
.IP "ftpstats_period" 2
.IX Item "ftpstats_period"
Statistics about downloads are truncated by size and period
simultaneously.
.Sp
How many days shall we keep statistics about downloads?
.IP "ftpstats_size" 2
.IX Item "ftpstats_size"
Statistics about downloads are truncated by size and period
simultaneously. Setting this to zero or negative disables download
statistics.
.Sp
How many items shall we keep in the statistics about downloads?
.IP "getcwd" 2
.IX Item "getcwd"
\&\s-1CPAN\s0.pm changes the current working directory often and needs to
determine its own current working directory. Per default it uses
Cwd::cwd but if this doesn't work on your system for some reason,
alternatives can be configured according to the following table:
.Sp
.Vb 5
\&    cwd         Cwd::cwd
\&    getcwd      Cwd::getcwd
\&    fastcwd     Cwd::fastcwd
\&    getdcwd     Cwd::getdcwd
\&    backtickcwd external command cwd
.Ve
.Sp
Preferred method for determining the current working directory?
.IP "halt_on_failure" 2
.IX Item "halt_on_failure"
Normally, \s-1CPAN\s0.pm continues processing the full list of targets and
dependencies, even if one of them fails.  However, you can specify
that \s-1CPAN\s0 should halt after the first failure.  (Note that optional
recommended or suggested modules that fail will not cause a halt.)
.Sp
Do you want to halt on failure (yes/no)?
.IP "histfile" 2
.IX Item "histfile"
If you have one of the readline packages (Term::ReadLine::Perl,
Term::ReadLine::Gnu, possibly others) installed, the interactive \s-1CPAN\s0
shell will have history support. The next two questions deal with the
filename of the history file and with its size. If you do not want to
set this variable, please hit \s-1SPACE\s0 \s-1ENTER\s0 to the following question.
.Sp
File to save your history?
.IP "histsize" 2
.IX Item "histsize"
Number of lines to save?
.IP "inactivity_timeout" 2
.IX Item "inactivity_timeout"
Sometimes you may wish to leave the processes run by \s-1CPAN\s0 alone
without caring about them. Because the Makefile.PL or the Build.PL
sometimes contains question you're expected to answer, you can set a
timer that will kill a 'perl Makefile.PL' process after the specified
time in seconds.
.Sp
If you set this value to 0, these processes will wait forever. This is
the default and recommended setting.
.Sp
Timeout for inactivity during {Makefile,Build}.PL?
.IP "index_expire" 2
.IX Item "index_expire"
The \s-1CPAN\s0 indexes are usually rebuilt once or twice per hour, but the
typical \s-1CPAN\s0 mirror mirrors only once or twice per day. Depending on
the quality of your mirror and your desire to be on the bleeding edge,
you may want to set the following value to more or less than one day
(which is the default). It determines after how many days \s-1CPAN\s0.pm
downloads new indexes.
.Sp
Let the index expire after how many days?
.IP "inhibit_startup_message" 2
.IX Item "inhibit_startup_message"
When the \s-1CPAN\s0 shell is started it normally displays a greeting message
that contains the running version and the status of readline support.
.Sp
Do you want to turn this message off?
.IP "keep_source_where" 2
.IX Item "keep_source_where"
Unless you are accessing the \s-1CPAN\s0 on your filesystem via a file: \s-1URL\s0,
\&\s-1CPAN\s0.pm needs to keep the source files it downloads somewhere. Please
supply a directory where the downloaded files are to be kept.
.Sp
Download target directory?
.IP "load_module_verbosity" 2
.IX Item "load_module_verbosity"
When \s-1CPAN\s0.pm loads a module it needs for some optional feature, it
usually reports about module name and version. Choose 'v' to get this
message, 'none' to suppress it.
.Sp
Verbosity level for loading modules (none or v)?
.IP "makepl_arg" 2
.IX Item "makepl_arg"
Every Makefile.PL is run by perl in a separate process. Likewise we
run 'make' and 'make install' in separate processes. If you have
any parameters (e.g. \s-1PREFIX\s0, \s-1UNINST\s0 or the like) you want to
pass to the calls, please specify them here.
.Sp
If you don't understand this question, just press \s-1ENTER\s0.
.Sp
Typical frequently used settings:
.Sp
.Vb 1
\&    PREFIX=~/perl    # non\-root users (please see manual for more hints)
.Ve
.Sp
Parameters for the 'perl Makefile.PL' command?
.IP "make_arg" 2
.IX Item "make_arg"
Parameters for the 'make' command? Typical frequently used setting:
.Sp
.Vb 1
\&    \-j3              # dual processor system (on GNU make)
.Ve
.Sp
Your choice:
.IP "make_install_arg" 2
.IX Item "make_install_arg"
Parameters for the 'make install' command?
Typical frequently used setting:
.Sp
.Vb 2
\&    UNINST=1         # to always uninstall potentially conflicting files
\&                     # (but do NOT use with local::lib or INSTALL_BASE)
.Ve
.Sp
Your choice:
.IP "make_install_make_command" 2
.IX Item "make_install_make_command"
Do you want to use a different make command for 'make install'?
Cautious people will probably prefer:
.Sp
.Vb 5
\&    su root \-c make
\& or
\&    sudo make
\& or
\&    /path1/to/sudo \-u admin_account /path2/to/make
.Ve
.Sp
or some such. Your choice:
.IP "mbuildpl_arg" 2
.IX Item "mbuildpl_arg"
A Build.PL is run by perl in a separate process. Likewise we run
\&'./Build' and './Build install' in separate processes. If you have any
parameters you want to pass to the calls, please specify them here.
.Sp
Typical frequently used settings:
.Sp
.Vb 1
\&    \-\-install_base /home/xxx             # different installation directory
.Ve
.Sp
Parameters for the 'perl Build.PL' command?
.IP "mbuild_arg" 2
.IX Item "mbuild_arg"
Parameters for the './Build' command? Setting might be:
.Sp
.Vb 1
\&    \-\-extra_linker_flags \-L/usr/foo/lib  # non\-standard library location
.Ve
.Sp
Your choice:
.IP "mbuild_install_arg" 2
.IX Item "mbuild_install_arg"
Parameters for the './Build install' command? Typical frequently used
setting:
.Sp
.Vb 2
\&    \-\-uninst 1       # uninstall conflicting files
\&                     # (but do NOT use with local::lib or INSTALL_BASE)
.Ve
.Sp
Your choice:
.IP "mbuild_install_build_command" 2
.IX Item "mbuild_install_build_command"
Do you want to use a different command for './Build install'? Sudo
users will probably prefer:
.Sp
.Vb 5
\&    su root \-c ./Build
\& or
\&    sudo ./Build
\& or
\&    /path1/to/sudo \-u admin_account ./Build
.Ve
.Sp
or some such. Your choice:
.IP "pager" 2
.IX Item "pager"
What is your favorite pager program?
.IP "prefer_installer" 2
.IX Item "prefer_installer"
When you have Module::Build installed and a module comes with both a
Makefile.PL and a Build.PL, which shall have precedence?
.Sp
The main two standard installer modules are the old and well
established ExtUtils::MakeMaker (for short: \s-1EUMM\s0) which uses the
Makefile.PL. And the next generation installer Module::Build (\s-1MB\s0)
which works with the Build.PL (and often comes with a Makefile.PL
too). If a module comes only with one of the two we will use that one
but if both are supplied then a decision must be made between \s-1EUMM\s0 and
\&\s-1MB\s0. See also http://rt.cpan.org/Ticket/Display.html?id=29235 for a
discussion about the right default.
.Sp
Or, as a third option you can choose \s-1RAND\s0 which will make a random
decision (something regular \s-1CPAN\s0 testers will enjoy).
.Sp
In case you can choose between running a Makefile.PL or a Build.PL,
which installer would you prefer (\s-1EUMM\s0 or \s-1MB\s0 or \s-1RAND\s0)?
.IP "prefs_dir" 2
.IX Item "prefs_dir"
\&\s-1CPAN\s0.pm can store customized build environments based on regular
expressions for distribution names. These are \s-1YAML\s0 files where the
default options for \s-1CPAN\s0.pm and the environment can be overridden and
dialog sequences can be stored that can later be executed by an
Expect.pm object. The \s-1CPAN\s0.pm distribution comes with some prefab \s-1YAML\s0
files that cover sample distributions that can be used as blueprints
to store your own prefs. Please check out the distroprefs/ directory of
the \s-1CPAN\s0.pm distribution to get a quick start into the prefs system.
.Sp
Directory where to store default options/environment/dialogs for
building modules that need some customization?
.IP "prerequisites_policy" 2
.IX Item "prerequisites_policy"
The \s-1CPAN\s0 module can detect when a module which you are trying to build
depends on prerequisites. If this happens, it can build the
prerequisites for you automatically ('follow'), ask you for
confirmation ('ask'), or just ignore them ('ignore').  Choosing
\&'follow' also sets \s-1PERL_AUTOINSTALL\s0 and \s-1PERL_EXTUTILS_AUTOINSTALL\s0 for
\&\*(L"\-\-defaultdeps\*(R" if not already set.
.Sp
Please set your policy to one of the three values.
.Sp
Policy on building prerequisites (follow, ask or ignore)?
.IP "randomize_urllist" 2
.IX Item "randomize_urllist"
\&\s-1CPAN\s0.pm can introduce some randomness when using hosts for download
that are configured in the urllist parameter. Enter a numeric value
between 0 and 1 to indicate how often you want to let \s-1CPAN\s0.pm try a
random host from the urllist. A value of one specifies to always use a
random host as the first try. A value of zero means no randomness at
all. Anything in between specifies how often, on average, a random
host should be tried first.
.Sp
Randomize parameter
.IP "recommends_policy" 2
.IX Item "recommends_policy"
(Experimental feature!) Some \s-1CPAN\s0 modules recommend additional, optional dependencies.  These should
generally be installed except in resource constrained environments.  When this
policy is true, recommended modules will be included with required modules.
.Sp
Include recommended modules?
.IP "scan_cache" 2
.IX Item "scan_cache"
By default, each time the \s-1CPAN\s0 module is started, cache scanning is
performed to keep the cache size in sync ('atstart'). Alternatively,
scanning and cleanup can happen when \s-1CPAN\s0 exits ('atexit'). To prevent
any cache cleanup, answer 'never'.
.Sp
Perform cache scanning ('atstart', 'atexit' or 'never')?
.IP "shell" 2
.IX Item "shell"
What is your favorite shell?
.IP "show_unparsable_versions" 2
.IX Item "show_unparsable_versions"
During the 'r' command \s-1CPAN\s0.pm finds modules without version number.
When the command finishes, it prints a report about this. If you
want this report to be very verbose, say yes to the following
variable.
.Sp
Show all individual modules that have no \f(CW$VERSION\fR?
.IP "show_upload_date" 2
.IX Item "show_upload_date"
The 'd' and the 'm' command normally only show you information they
have in their in-memory database and thus will never connect to the
internet. If you set the 'show_upload_date' variable to true, 'm' and
\&'d' will additionally show you the upload date of the module or
distribution. Per default this feature is off because it may require a
net connection to get at the upload date.
.Sp
Always try to show upload date with 'd' and 'm' command (yes/no)?
.IP "show_zero_versions" 2
.IX Item "show_zero_versions"
During the 'r' command \s-1CPAN\s0.pm finds modules with a version number of
zero. When the command finishes, it prints a report about this. If you
want this report to be very verbose, say yes to the following
variable.
.Sp
Show all individual modules that have a \f(CW$VERSION\fR of zero?
.IP "suggests_policy" 2
.IX Item "suggests_policy"
(Experimental feature!) Some \s-1CPAN\s0 modules suggest additional, optional dependencies.  These 'suggest'
dependencies provide enhanced operation.  When this policy is true, suggested
modules will be included with required modules.
.Sp
Include suggested modules?
.IP "tar_verbosity" 2
.IX Item "tar_verbosity"
When \s-1CPAN\s0.pm uses the tar command, which switch for the verbosity
shall be used? Choose 'none' for quiet operation, 'v' for file
name listing, 'vv' for full listing.
.Sp
Tar command verbosity level (none or v or vv)?
.IP "term_is_latin" 2
.IX Item "term_is_latin"
The next option deals with the charset (a.k.a. character set) your
terminal supports. In general, \s-1CPAN\s0 is English speaking territory, so
the charset does not matter much but some \s-1CPAN\s0 have names that are
outside the \s-1ASCII\s0 range. If your terminal supports \s-1UTF\-8\s0, you should
say no to the next question. If it expects \s-1ISO\-8859\-1\s0 (also known as
\&\s-1LATIN1\s0) then you should say yes. If it supports neither, your answer
does not matter because you will not be able to read the names of some
authors anyway. If you answer no, names will be output in \s-1UTF\-8\s0.
.Sp
Your terminal expects \s-1ISO\-8859\-1\s0 (yes/no)?
.IP "term_ornaments" 2
.IX Item "term_ornaments"
When using Term::ReadLine, you can turn ornaments on so that your
input stands out against the output from \s-1CPAN\s0.pm.
.Sp
Do you want to turn ornaments on?
.IP "test_report" 2
.IX Item "test_report"
The goal of the \s-1CPAN\s0 Testers project (http://testers.cpan.org/) is to
test as many \s-1CPAN\s0 packages as possible on as many platforms as
possible.  This provides valuable feedback to module authors and
potential users to identify bugs or platform compatibility issues and
improves the overall quality and value of \s-1CPAN\s0.
.Sp
One way you can contribute is to send test results for each module
that you install.  If you install the CPAN::Reporter module, you have
the option to automatically generate and deliver test reports to \s-1CPAN\s0
Testers whenever you run tests on a \s-1CPAN\s0 package.
.Sp
See the CPAN::Reporter documentation for additional details and
configuration settings.  If your firewall blocks outgoing traffic,
you may need to configure CPAN::Reporter before sending reports.
.Sp
Generate test reports if CPAN::Reporter is installed (yes/no)?
.IP "perl5lib_verbosity" 2
.IX Item "perl5lib_verbosity"
When \s-1CPAN\s0.pm extends \f(CW@INC\fR via \s-1PERL5LIB\s0, it prints a list of
directories added (or a summary of how many directories are
added).  Choose 'v' to get this message, 'none' to suppress it.
.Sp
Verbosity level for \s-1PERL5LIB\s0 changes (none or v)?
.IP "prefer_external_tar" 2
.IX Item "prefer_external_tar"
Per default all untar operations are done with the perl module
Archive::Tar; by setting this variable to true the external tar
command is used if available; on Unix this is usually preferred
because they have a reliable and fast gnutar implementation.
.Sp
Use the external tar program instead of Archive::Tar?
.IP "trust_test_report_history" 2
.IX Item "trust_test_report_history"
When a distribution has already been tested by CPAN::Reporter on
this machine, \s-1CPAN\s0 can skip the test phase and just rely on the
test report history instead.
.Sp
Note that this will not apply to distributions that failed tests
because of missing dependencies.  Also, tests can be run
regardless of the history using \*(L"force\*(R".
.Sp
Do you want to rely on the test report history (yes/no)?
.IP "urllist_ping_external" 2
.IX Item "urllist_ping_external"
When automatic selection of the nearest cpan mirrors is performed,
turn on the use of the external ping via Net::Ping::External. This is
recommended in the case the local network has a transparent proxy.
.Sp
Do you want to use the external ping command when autoselecting
mirrors?
.IP "urllist_ping_verbose" 2
.IX Item "urllist_ping_verbose"
When automatic selection of the nearest cpan mirrors is performed,
this option can be used to turn on verbosity during the selection
process.
.Sp
Do you want to see verbosity turned on when autoselecting mirrors?
.IP "use_prompt_default" 2
.IX Item "use_prompt_default"
When this is true, \s-1CPAN\s0 will set \s-1PERL_MM_USE_DEFAULT\s0 to a true
value.  This causes ExtUtils::MakeMaker (and compatible) prompts
to use default values instead of stopping to prompt you to answer
questions. It also sets \s-1NONINTERACTIVE_TESTING\s0 to a true value to
signal more generally that distributions should not try to
interact with you.
.Sp
Do you want to use prompt defaults (yes/no)?
.IP "use_sqlite" 2
.IX Item "use_sqlite"
CPAN::SQLite is a layer between the index files that are downloaded
from the \s-1CPAN\s0 and \s-1CPAN\s0.pm that speeds up metadata queries and reduces
memory consumption of \s-1CPAN\s0.pm considerably.
.Sp
Use CPAN::SQLite if available? (yes/no)?
.IP "version_timeout" 2
.IX Item "version_timeout"
This timeout prevents \s-1CPAN\s0 from hanging when trying to parse a
pathologically coded \f(CW$VERSION\fR from a module.
.Sp
The default is 15 seconds.  If you set this value to 0, no timeout
will occur, but this is not recommended.
.Sp
Timeout for parsing module versions?
.IP "yaml_load_code" 2
.IX Item "yaml_load_code"
Both \s-1YAML\s0.pm and YAML::Syck are capable of deserialising code. As this
requires a string eval, which might be a security risk, you can use
this option to enable or disable the deserialisation of code via
CPAN::DeferredCode. (Note: This does not work under perl 5.6)
.Sp
Do you want to enable code deserialisation (yes/no)?
.IP "yaml_module" 2
.IX Item "yaml_module"
At the time of this writing (2009\-03) there are three \s-1YAML\s0
implementations working: \s-1YAML\s0, YAML::Syck, and \s-1YAML::XS\s0. The latter
two are faster but need a C compiler installed on your system. There
may be more alternative \s-1YAML\s0 conforming modules. When I tried two
other players, YAML::Tiny and YAML::Perl, they seemed not powerful
enough to work with \s-1CPAN\s0.pm. This may have changed in the meantime.
.Sp
Which \s-1YAML\s0 implementation would you prefer?
.SH "LICENSE"
.IX Header "LICENSE"
This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.

Copyright 2K16 - 2K18 Indonesian Hacker Rulez