Re: @INC paths for TAP::Harness

# from David E. Wheeler
# on Wednesday 09 July 2008 09:51:

>> (For some value of 'work' -- that's a major wreck right now for
>> Module::Build's tests -- some assumption about blib/lib is wrong?)
>
>Um, what?

TAP::Harness doesn't force the caller's @INC into subprocesses the way 
Test::Harness did, so it needs to be explicitly passed as 'libs => 
[@INC]' -- though we might want to clean that up a bit to have e.g. 
only 'blib/lib'?.

I'm not finding much documentation about the include path for tests.  Is 
there a presumed API in play or would it be fair to simply restrict the 
tests' @INC to blib/{lib,arch} ?  (Plus some API parameter 
like 'include_path'?)

--Eric
-- 
But as soon as you hear the Doppler shift dropping in pitch, you know
that they're probably going to miss your house, because if they were on
a collision course with your house, the pitch would stay the same until
impact. As I said, that one's subtle.
--Larry Wall
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------