Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Sub-Exporter-Progressive CPAN distribution.

Report information
The Basics
Id: 78719
Status: resolved
Priority: 0/
Queue: Sub-Exporter-Progressive

People
Owner: Nobody in particular
Requestors: w.phillip.moore [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.001002
Fixed in: (no value)



Subject: Unspecified dependency on Sub::Exporter results in test suite failure
The dependency on Sub::Exporter isn't specified, since the whole point of this module is to make it optional, but you *do* require it in the test suite. That means you can install this module and use it without Sub::Exporter, but you can't test it. The test suite fails with: [2012-08-01 13:46:53] your usage of Sub::Exporter::Progressive requires Sub::Exporter to be installed at /var/tmp/perl5-Sub-Exporter-Progressive-0.001002-build001-build/x86- 64.rhel.5/5.14/source/Sub-Exporter-Progressive- 0.001002/blib/lib/Sub/Exporter/Progressive.pm line 34. [2012-08-01 13:46:53] BEGIN failed--compilation aborted at t/sex.t line 11. [2012-08-01 13:46:53] t/sex.t ................. [2012-08-01 13:46:53] Dubious, test returned 2 (wstat 512, 0x200) [2012-08-01 13:46:53] No subtests run [2012-08-01 13:46:53] [2012-08-01 13:46:53] Test Summary Report [2012-08-01 13:46:53] ------------------- [2012-08-01 13:46:53] t/sex.t (Wstat: 512 Tests: 0 Failed: 0) (timestamps are from my build system's logs) To resolve this, I think you can probably get away with specifying Sub::Exporter as a test dependency, or you could just refine it a normal runtime dependency. Alternately, make that entire test conditional on Sub::Exporter being installed at all. I suspect you didn't see this simply because you probably built and tested this in an environment where S::E was already installed.
This is fixed in newer releases.