Hi, Just some quick comments:
Regarding the PoCos (namely the POE::Component::CPAN* modules and
POE::Component::SmokeBox)
- They don't care about the configuration data of the smoke framework that
they are testing
- They live in a separate perl installation to the one being tested
The pocos merely hand the smoking framework, be it CPAN(PLUS)::YACSmoke,
CPAN::Reporter ( via CPAN)
or CPAN::Reporter::Smoker, the thing to be smoked and monitor that smoke
process watching for
stalled smokes, run-away looped smokes, etc. ( killing the process as
appropriate ).
So, I can confidently say that they are outside the scope of this discussion.
Regarding CPANPLUS::YACSmoke ( and CPAN::YACSmoke ).
CPANPLUS::YACSmoke looks for its config file (cpansmoke.ini) and its history
database (cpansmoke.dat.*)
in the same place that CPANPLUS stores its configuration/sources/build.
CPANPLUS uses the APPDATA HOME USERPROFILE WINDIR SYS$LOGIN env vars in that
order to check for its config.
my @os_home_envs = qw( APPDATA HOME USERPROFILE WINDIR SYS$LOGIN );
for my $env ( @os_home_envs ) {
next unless exists $ENV{ $env };
next unless defined $ENV{ $env } && length $ENV{ $env };
return $ENV{ $env } if -d $ENV{ $env };
}
Anyways.
CPANPLUS::YACSmoke uses SDBM_File for its history file.
distribution-version => (pass|fail|aborted|na)
The only thing that CPANPLUS::YACSmoke uses from the cpansmoke.ini file is the
exclude lists:
( it uses Config::IniFiles )
[CONFIG]
exclude_dists=<<HERE
mod_perl
HERE
Cheers,
--
Chris Williams
aka BinGOs
PGP ID 0x4658671F
http://www.gumbynet.org.uk
==========================
pgp0Sz1vuJeVz.pgp
Description: PGP signature
