[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl-module-build
Subject:    Re: @INC paths for TAP::Harness
From:       "David E. Wheeler" <david () kineticode ! com>
Date:       2008-07-09 22:56:29
Message-ID: 52EC204D-0D51-48D8-A03D-0485D573FCCA () kineticode ! com
[Download RAW message or body]

On Jul 9, 2008, at 14:25, Eric Wilhelm wrote:

> But alas, like Test::Harness, we have perpetuated a culture of  
> assuming
> that your @INC always magically appears in the child process --
> including in M::B's own code.  That might be unsurprising most of the
> time, but it does make a certain class of setups relatively  
> impossible.

Well, perhaps we shouldn't perpetuate that for TAP::Harness usage, eh?

> Anyway, I've decided that doing anything more correct is made of suck
> and would just require me to explain it too often, so I will just be
> foisting @INC into the test.
>
> I'm nearly certain it will break on redhat.

I think it's the other way around: redhat is broken. ;-P

Best,

David

[prev in list] [next in list] [prev in thread] [next in thread]