Re: @INC paths for TAP::Harness
[email protected] (Eric Wilhelm)
| Newsgroups | perl.module.build |
|---|---|
| Message-ID | <[email protected]> |
# from David E. Wheeler
# on Wednesday 09 July 2008 11:35:
>> 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'?.
>
>Makes sense to me. Though it did work fine the way I had it. I wonder
> why it wasn't a problem?
You were not running './Build test --use-tap-harness' for Module::Build
because I am still sitting on the make-that-an--option code.
--Eric
--
"It is a mistake to allow any mechanical object to realize that you are
in a hurry."
--Ralph's Observation
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------