Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Test-Prereq CPAN distribution.

Report information
The Basics
Id: 61322
Status: open
Priority: 0/
Queue: Test-Prereq

People
Owner: Nobody in particular
Requestors: SILASMONK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.037
Fixed in: (no value)



Subject: Could modules used inside an exclusded module be checked?
I got burnt with Test::CGI::Multipart. This has a module Utils in t/lib which is of course excluded from prerequisite testing -- not least because it is actually shipped with the module. However Perl6::Slurp is used from within Utils and this build dependency got missed in version v0.0.1. Probably even smarter behaviour would be to recognise that modules in the t directory are actually being shipped with the module.
On Tue Sep 14 04:16:00 2010, SILASMONK wrote: Show quoted text
> I got burnt with Test::CGI::Multipart. This has a module Utils in t/lib > which is of course excluded from prerequisite testing -- not least > because it is actually shipped with the module. However Perl6::Slurp is > used from within Utils and this build dependency got missed in version > v0.0.1.
I think I have a fix for this in the tlib branch in github. http://github.com/briandfoy/test-prereq/tree/tlib
Brian, Thanks for getting back to me so quickly on this. This worked after I had persuaded git to really download the tlib branch. Two questions. 1.) What's with the comment about Test::Manifest version 2.00? And what are your plans for all those debugging statements?
On Tue Sep 14 18:52:10 2010, SILASMONK wrote: Show quoted text
> Thanks for getting back to me so quickly on this. This worked after I > had persuaded git to really download the tlib branch. Two questions. 1.) > What's with the comment about Test::Manifest version 2.00?
Well, I was hacking on Test:Prereq last week, so on my development branch it's using an unreleased module in its test suite. Both of those will get pushed out at the same time. Since this looks like it might solve your problem, I'll fix up the rough edges and merge it back into master. Show quoted text
> And what are > your plans for all those debugging statements?
I was thinking of leaving the debugging statements in there. I just have to give you a way to turn them on when you need them.