MAJOR=4
MINOR=8
DEVNAME=tty8
þ File not found.
0 li~ *h 6p Tţ
u_ ub
&=LV[( ? # -*- Mode: cperl; coding: utf-8; cperl-indent-level: 4 -*-
# vim: ts=4 sts=4 sw=4:
package CPAN::FirstTime;
use strict;
use ExtUtils::MakeMaker ();
use FileHandle ();
use File::Basename ();
use File::Path ();
use File::Spec ();
use CPAN::Mirrors ();
use CPAN::Version ();
use vars qw($VERSION $auto_config);
$VERSION = "5.5316";
=head1 NAME
CPAN::FirstTime - Utility for CPAN::Config file Initialization
=head1 SYNOPSIS
CPAN::FirstTime::init()
=head1 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).
In the following all questions and explanations regarding config
variables are collected.
=cut
# down until the next =back the manpage must be parsed by the program
# because the text is used in the init dialogues.
my @podpara = split /\n\n/, <<'=back';
=over 2
=item allow_installing_module_downgrades
The CPAN shell can watch the C directories that are built up
before running C 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.
Do you want to allow installing distros with decreasing module
versions compared to what you have installed (yes, no, ask/yes,
ask/no)?
=item allow_installing_outdated_dists
The CPAN shell can watch the C directories that are built up
before running C 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.
Note: choosing anything but 'yes' for this option will need
CPAN::DistnameInfo being installed for taking effect.
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)?
=item auto_commit
Normally CPAN.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.
Always commit changes to config variables to disk?
=item build_cache
CPAN.pm can limit the size of the disk area for keeping the build
directories with all the intermediate files.
Cache size for build directory (in MB)?
=item build_dir
Directory where the build process takes place?
=item build_dir_reuse
Until version 1.88 CPAN.pm never trusted the contents of the build_dir
directory between sessions. Since 1.88_58 CPAN.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.
If you say yes to the following question, CPAN 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.
Store and re-use state information about distributions between
CPAN.pm sessions?
=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.
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)