App-Framework

 view release on metacpan or  search on metacpan

Makefile.PL  view on Meta::CPAN

from the following which $mod modules you would like to be fully installed and tested (any modules
you do not select will still be available but you will have to manually install any module dependencies).

The optional modules are:
MSG

for my $num (sort { $a <=> $b } keys %optional) 
{
	printf "    [%d] %s - %s\n", $num, $optional{$num}{'name'}, $optional{$num}{'description'} ;
}
my $c = prompt("\nEnter your choices, separated by spaces (0=none, a=all):", "a"); print "\n";


my %to_install ;
if ($c)
{
	if ($c =~ /a/i)
	{
		for my $num (keys %optional) 
		{
			$to_install{$num} = 1 ;

inc/Module/Install/Makefile.pm  view on Meta::CPAN

BEGIN {
	$VERSION = '1.16';
	@ISA     = 'Module::Install::Base';
	$ISCORE  = 1;
}

sub Makefile { $_[0] }

my %seen = ();

sub prompt {
	shift;

	# Infinite loop protection
	my @c = caller();
	if ( ++$seen{"$c[1]|$c[2]|$_[0]"} > 3 ) {
		die "Caught an potential prompt infinite loop ($c[1]|$c[2]|$_[0])";
	}

	# In automated testing or non-interactive session, always use defaults
	if ( ($ENV{AUTOMATED_TESTING} or -! -t STDIN) and ! $ENV{PERL_MM_USE_DEFAULT} ) {
		local $ENV{PERL_MM_USE_DEFAULT} = 1;
		goto &ExtUtils::MakeMaker::prompt;
	} else {
		goto &ExtUtils::MakeMaker::prompt;
	}
}

# Store a cleaned up version of the MakeMaker version,
# since we need to behave differently in a variety of
# ways based on the MM version.
my $makemaker = eval $ExtUtils::MakeMaker::VERSION;

# If we are passed a param, do a "newer than" comparison.
# Otherwise, just return the MakeMaker version.

t/20-Feature-Config.t  view on Meta::CPAN

	{
		'port'		=> 32161,
		'logfile'	=> '/tmp/ate_snmp.log',
	},
	],
	'tty'		=> [
	{
		name 		=> 'SC2-1', 		
		host 		=> 'tty-server2',
		port 		=> 2011, 
		prompt 		=> '/SC2-HWTC\s*>/i', 
		timeout		=> 90,
	},
	{
		name 		=> 'BBU-1',
		host 		=> 'tty-server2',
		port 		=> 2012, 
		prompt 		=> '/(RSS|\-)\s*>/i', 
		timeout		=> 90,
	},
	{
		name 		=> 'SC2-2', 		
		host 		=> 'tty-server2',
		port 		=> 2013, 
		prompt 		=> '/SC2-HWTC\s*>/i', 
		timeout		=> 90,
	},
	{
		name 		=> 'BBU-2', 		
		host 		=> 'tty-server2',
		port 		=> 2014, 
		prompt 		=> '/(RSS|\-)\s*>/i', 
		timeout		=> 90,
	},
	],
	'snmp'		=> [
	{
		name 		=> 'CTU4-1', 		
		host 		=> 'ctu4-1',
	},
	{
		name 		=> 'CTU4-2', 		

t/config2/20-Feature-Config.conf  view on Meta::CPAN

#
# Each section is of the form:
#
# [tty]
# # Name to use for the session. This name is used when communicating to the device
# name 		= SC2 		
# # IP address (or name) of the Cisco tty server
# host 		= tty-server
# # Telnet port to use on the Cisco tty server (port is 2000 + tty number)
# port 		= 2001 
# # Expected prompt from the connected device
# prompt 		= /SC2-HWTC\s*>\s*$/i 
#
# Along with mandatory setting, if the target device requires a login then the following must also 
# be specified:
#
# # User name
# user		= sdprice1
# # Password
# password	= password 
#

[tty]
name 		= SC2-1 		
host 		= tty-server2
port 		= 2011 
prompt 		= /SC2-HWTC\s*>/i 
timeout		= 90

[tty]
name 		= BBU-1 		
host 		= tty-server2
port 		= 2012 
prompt 		= /(RSS|\-)\s*>/i 
timeout		= 90

[tty]
name 		= SC2-2 		
host 		= tty-server2
port 		= 2013 
prompt 		= /SC2-HWTC\s*>/i 
timeout		= 90

[tty]
name 		= BBU-2 		
host 		= tty-server2
port 		= 2014 
prompt 		= /(RSS|\-)\s*>/i 
timeout		= 90



##--------------------------------------------------------------------------------------------------
## snmp section
#
# Creates an SNMP session with the specified host.
#
# Each section is of the form: