Skip Menu |

This queue is for tickets about the CHI CPAN distribution.

Report information
The Basics
Id: 98830
Status: new
Priority: 0/
Queue: CHI

Owner: Nobody in particular
Requestors: KENTNL [...]

Bug Information
Severity: (no value)
Broken in: 0.58
Fixed in: (no value)

Subject: CHI::Test system a bit messy for dependency resolution
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-31416-1410524077-531.0-0-0 [...]>
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 1508

1. CHI::Test and friends are currently expressly "no-indexed", so they can't be depended upon.
2. =~ Autoprereq generators are thus "right", but need hand adjustment to work.
3. Dependencies of CHI::Test are not considered Runtime dependencies, But Test dependencies.

This is true for CHI itself to an extent, but for anything *consuming* CHI::Test, those Test dependencies should be considered "CHI::Test runtime dependencies"

The net result of these have some unfortunate side effects:


 For instance, if I'm testing a module prior to ship with travis, all the dependencies themselves will be installed with '--notest', which means CHI's TEST_REQUIRES don't get pulled, because they're deemed not needed. ( Because we're not testing CHI itself, only a thing that *uses* CHI )

And then they'll execute CHI::Test and friends as part of the test, and fail due to the dependencies being missing:; # Fails because Test::Deep is not installed; # Fails because Date::Parse is not installed

This essentially means everyone who consumes CHI::Test has to also forwards declare CHI::Test's dependencies, and that doesn't seem very perlish to me =).



This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to