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
