Thanks to all who offered advice on this list. I have implemented all
the changes discussed and wait with eager anticipation my cpan-test
results :-)
Martin
David Golden wrote:
On Nov 14, 2007 3:01 AM, Graham TerMarsch <[EMAIL PROTECTED]> wrote:
its no there. The trick here is to (a) not generate any sort of Makefile or
Build, and (b) to "exit 0" (no error condition). This'll turn CPAN
Tester "FAIL"s into "NA"s so they're at least not a total black mark against
what you're seeing. Still sucks IMHO, but its at least better than a
failure.
It's actually even better -- it doesn't (shouldn't) generate any
report at all. It's a "please gently stop" way to halt things.
Note -- from a testing perspective, CPAN::Reporter requires a version
of CPAN that supports configure_requires. Once CPANPLUS supports it
as well, then the next version of CPAN::YACSmoke could require that
version of CPANPLUS and then anyone with an upgraded testing setup
will support configure_requires. That should avoid a number of CPAN
Testers FAIL reports -- though it may or may not help the poor end
user.
David
