Skip Menu |

This queue is for tickets about the ExtUtils-MakeMaker CPAN distribution.

Report information
The Basics
Id: 39650
Status: rejected
Priority: 0/
Queue: ExtUtils-MakeMaker

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

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



Subject: TAP::Harness in EU::MM
Date: Sat, 27 Sep 2008 22:42:45 -0700
To: bug-extutils-makemaker [...] rt.cpan.org
From: "David E. Wheeler" <dwheeler [...] cpan.org>
Heya, Following up on my patch to Module::Build to add support for Test::Harness, here's a patch that does the same thing for EU::MM. Sure it will have portability problems, but I think you'd have to have a pretty new Perl to use TAP::Harness, anyway, eh? So, what does this break beyond all belief? I don't think that it will break anything except for those perhaps users who try to use it with an older Perl or somewhere where TAP::Harness or Data::Dumper aren't available or don't run. Let me know what you think. Best, David

Message body is not shown because sender requested not to inline it.

Remind me again why we want special TAP::Harness support? It appears to do exactly the same thing as Test::Harness. Is it just to pass parameters through to TAP::Harness->new?
Subject: Re: [rt.cpan.org #39650] TAP::Harness in EU::MM
Date: Sun, 28 Sep 2008 08:06:47 -0700
To: "bug-ExtUtils-MakeMaker [...] rt.cpan.org" <bug-ExtUtils-MakeMaker [...] rt.cpan.org>
From: "David E. Wheeler" <david [...] kineticode.com>
Yes, so that I can tell it how to run tests not written in Perl (e.g. pgTAP). Best, David Sent from my iPhone On Sep 27, 2008, at 23:27, "Michael G Schwern via RT" <bug-ExtUtils-MakeMaker@rt.cpan.org Show quoted text
> wrote:
Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=39650 > > > Remind me again why we want special TAP::Harness support? It > appears to > do exactly the same thing as Test::Harness. Is it just to pass > parameters through to TAP::Harness->new?
Sorry, I don't want to put special case code into MakeMaker for special test harnesses. I think it's more an inflexibility on TAP::Harness' part that you would need this. See http://rt.cpan.org/Ticket/Display.html?id=39984 for a potential fix at the TAP::Harness level.