Re: @INC paths for TAP::Harness
[email protected] ("David E. Wheeler")
| Newsgroups | perl.module.build |
|---|---|
| Message-ID | <[email protected]> |
On Jul 9, 2008, at 10:15, Eric Wilhelm wrote:
> 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?
> 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'?)
That I don't know. What does EU::MM do?
Best,
David