develop prereqs are being reported, which is confusing (not all modules listed will be installed by the end-user running tests), and unnecessary -- by default this test should only report test and runtime requires (it could possibly report develop, and recommended modules, in separate sections). From #distzilla: 00:07 < kentnl> ether_: http://www.cpantesters.org/cpan/report/0bf5a750-0a72-11e3-bc3a-aa575326ef19 # Looks like something in Test::Kwalitee is causing ReportVersions::Tiny to fail 00:07 < dipsy> [ CPAN Testers Reports: Report for Dist-Zilla-App-Command-dumpphases-0.2.0 ] 00:08 < kentnl> its weirdly only throwing that problem now because RV:Tiny shows develop_requires 00:08 < kentnl> and previously it didn't show in develop_requires 00:11 < kentnl> so its failing because there's an old version of something, but I don't even myself specify that that something is required 00:11 < kentnl> so there's no way I can fix it other than having a mandatory dep on Test::Kwaltiee, which is not something I'm fond of doing 00:12 < kentnl> essentially, I've hit a technical reason for why I don't like dists adding themselves to requirements lists. 03:05 < haarg> RV:Tiny really shouldn't output develop requirements, or at least have them listed separately 03:15 < kentnl> the problem here though is, even just listing it seperately causes a problem 04:26 < haarg> yeah, that's a separate issue 04:27 < haarg> the output in that test report ends up looking very confused though, because half of the listed dependencies aren't met 04:45 < kentnl> Its bugged me for a while, I just haven't had the tuits to do something better =) (the separate issue mentioned above is caused by the require() behaviour - some test modules, e.g. Test::Kwalitee, Test::Pod have side effects from loading them.)