Christopher H. Laco wrote: > While trying to install the latest PPI from svn, I noticed that running > 'dmake test' passed, and 'prove -b t/' failed. > > As more and more people use Module::Install, it seems more and more > transient build/test related modules are being stuffed in the inc/ > directory. > > Given the talk about installers being installers (dmake) and testers > being testers (prove), what is the correct behavior in this situation?
Start using prove -b -Iinc ? > Should the tests be skipping when these modules aren't found, and stop > assuming I'm doing a 'make test' instead of a 'prove'? No, that defeats the point of putting them in inc/ so they're always there. If the tests were ok with skipping when the module isn't available they'd just make it an optional requirement rather than shipping with a copy. > Should prove -l or -b look for an inc/ directory as well? This might be a good idea. Or perhaps a more abstract "do the right thing" flag which does whatever is necessary to handle the various testing styles in vogue. Currently simply... -d 'blib/lib' ? set -b : set -l; set -Iinc if -d "inc";
