Hey Randy,
I think we're making progress here. The smoking script will not test a module if it's prereq's are not satisfied. So, if Apache::AuthCookieDBI correctly references prereq modules, and they are not installed (or the -p -chases down prereq modules- option is not given to the smoker), then Apache::AuthCookieDBI will not be tested. If the -p option is given, or in this case, Apache::AuthCookie is installed, the module will be tested. Hence, the request/requirement to fill out PREREQ_PM. So, there is no consistency problem with CPANPLUS scripts doing automated testing, IF the PREREQ_PM is complete. We there yet? Rob > > > 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... > > All I meant is that, if I followed the policy of failing a > package automatically if PREREQ_PM wasn't filled in properly, > then, in the current example (where Apache::AuthCookieDBI > requires Apache::AuthCookie), in testing Apache::AuthCookieDBI: > > - if I didn't have Apache::AuthCookie installed, then > Apache::AuthCookieDBI would automatically fail; > - if I happened to have Apache::AuthCookie installed, then > Apache::AuthCookieDBI wouldn't necessarily fail, at least > for reasons of this missing dependency. > > So the grade depends on if I happen to have installed, perhaps > for some unrelated purpose, Apache::AuthCookie. That's what I > meant by consistency - the grade would depend on the specific > installed modules present on the system at the time of testing, > and testing at another time when additional modules may have been > installed, or on an identical system with a different set of > non-standard modules, might change the grade. >
