File Coverage

blib/lib/CPAN/Access/AdHoc/Default/CPAN/CPAN.pm

Criterion	Covered	Total	%
statement	24	25	96.0
branch	2	4	50.0
condition	1	3	33.3
subroutine	6	7	85.7
pod	1	1	100.0
total	34	40	85.0

package CPAN::Access::AdHoc::Default::CPAN::CPAN;

use 5.008;

use strict;
use warnings;

use CPAN::Access::AdHoc::Util qw{ __load };

our $VERSION = '0.000_194';

my $configured = eval {
    __load( 'CPAN' );
    1;
};

sub get_default {
    my ( $class ) = @_;

    $configured
	or return;

    {
	# Okay, here's the deal on the monkey patch.
	#
	# There is, to the best of my research, no supported way to
	# prevent CPAN from initializing itself; there are just various
	# unsupported ways. As of CPAN::HandleConfig 5.5003 (with CPAN
	# 1.9800 07-Aug-2011) they are:
	#
	# * The monkey patch actually used. This exploits the fact that
	#   the load() method returns if the do_init argument is false
	#   (which it is by default) and there are no missing
	#   configuration items (which the monkey patch takes care of)
	# * Set $CPAN::HandleConfig::loading to a positive number. This
	#   is a guard against accidental recursion.
	#
	# Parse::CPAN::Packages::Fast by Slaven Rezic seems to make the
	# assumption you can get the same effect by setting
	# $CPAN::Be_Silent to a true value, but that is not how I read
	# the CPAN code.

	no warnings qw{ once redefine };	## no critic (ProhibitNoWarnings)
	local *CPAN::HandleConfig::missing_config_data = sub { return };
	CPAN::HandleConfig->load();
    }

    exists $CPAN::Config->{urllist}
	and @{ $CPAN::Config->{urllist} }
	or return;

    return @{ $CPAN::Config->{urllist} };
}

1;

__END__