Andy Armstrong wrote:
On 27 Jan 2007, at 19:10, Andy Armstrong wrote:
I've just committed a patch against ExtUtils::MakeMaker 6.31 that
makes test_harness use TAPx::Harness instead of Test::Harness if the
env variable PERL_EUMM_USE_TAPX is set to a true value and
TAPx::Harness is installed.
Andy Armstrong wrote:
I've just committed a patch against ExtUtils::MakeMaker 6.31 that makes
test_harness use TAPx::Harness instead of Test::Harness if the env
variable PERL_EUMM_USE_TAPX is set to a true value and TAPx::Harness is
installed.
EUMM Patch:
On 29 Jan 2007, at 12:41, Michael G Schwern wrote:
Umm, yeah. I was wondering about that.
Sorry for the confusion. The patch serves two purposes:
1) It makes it possible for people to try TAPx::Harness and easily
disable it if they run into problems
2) It's part of me working out the
On 29 Jan 2007, at 12:57, Michael G Schwern wrote:
EUMM Patch: http://svn.hexten.net/tapx/patches/ExtUtils-
MakeMaker-6.31.patch
I couldn't accept this patch to MM. This would lead to MM's
environment being littered with PERL_EUMM_USE_FLAVOR_OF_THE_WEEK.
And if TAPx::Harness is
--- Andy Armstrong [EMAIL PROTECTED] wrote:
Or if the condition for checking to use TAPx::Harness were more
complex you can figure it out beforehand and roll the decision up
into $use_tapx.
Yes indeed. But as you say it'd be nicer still to be able to plug in
any alternative
Andy Armstrong wrote:
Sure - I'm open to suggestions. Do you mean something like this?:
$ export PERL_EUMM_HARNESS_CLASS=TAPx::Harness::Compatible
$ make test
That's one way, though I'd rather it be a Makefile.PL argument. [1]
The way I was thinking was to make it easier for users to write
