On Sat, May 11, 2002 at 08:55:49PM -0600, Robert wrote:
> I'm going to go out on a limb here, but I'm sure I'll be
> corrected if I'm wrong.  I suspect that if a prereq module
> does not test PASS, that the module will not be tested at all.

This is correct. Failures at the Makefile.PL and 'make' stage
prevents cpansmoke from entering 'make test' stage, and hence
nothing will be reported.

> cpansmoke does a temp install of prereq modules, grading them
> as it goes along.

This is correct, modulo a small problem -- it doesn't make a
'temp install' at all. I merely add each prerequisite's
blib/lib and blib/arch directories into @INC, so that 'make
install' is never called -- the blib/ directories are built
by the 'make' target. This makes a prison (locked into the
..cpanplus directory) or additional permission control possible.

> Why do you say there will be a consistency problem?  I don't
> understand.  All required modules are temporarily installed,
> and unless there is a circular dependency...

....and CPANPLUS resolves circular dependency, core dependency
and self-dependency just fine...

> Hey, you can belabor all you want, as long as questions are
> asked, and points understood, I'm learning.

Same here. I'd argue that for the detectable "Insufficient
PREREQ_PM" and other common errors, we should still send
FAIL, but with a more helpful message as to how to correct
the problem (like the one I've written for the UNKNOWN report
of modules that did not specify their test suites, as included
after __DATA__).

Anybody interested in drafting a similiar notification letter
to the author of a module that runs into the PREREQ_PM problem?

Thanks,
/Autrijus/

__DATA__
Hello there! Thanks for uploading your $dist on CPAN.

Would it be too much to ask for a simple test script in
the next release of $module->{module}'s distribution, so
people can verify which platforms can successfully install
them, as well as avoid regression bugs?

A simple 't/use.t' that says:

#!/usr/bin/env perl -w
use strict;
use Test;
BEGIN { plan tests => 1 }

use Your::Module::Here; ok(1);
exit;
__END__

would be appreciated.  If you are interested in making a more robust
test suite, please see the Test::Simple, Test::More and Test::Tutorial
manpages at <http://search.cpan.org/search?dist=Test-Simple>.

Attachment: msg33348/pgp00000.pgp
Description: PGP signature

Reply via email to