[1175] The harness actually already sets up all the include paths correctly , so no

[Nicholas Clark]

On Tue, Aug 26, 2008 at 01:17:58AM -0700, Eric Wilhelm wrote:
> # from nicholas at hexten.net
> # on Tuesday 26 August 2008 00:46:
> 
> >The harness actually already sets up all the include paths correctly,
> > so no need to manually fiddle with them here.
> >
> > ...
> >-BEGIN {
> >-    if ( $ENV{PERL_CORE} ) {
> >-        unshift @INC, '../lib';
> >-    }
> >-}
> 
> Really?  I think this was cargo-culted from Module::Build.  Is this a 
> change in the core harness?

I can't answer whether it's a change. I can say that the tests still pass
when I take this code out, so I assume that the code I removed is vestigal,
rather than needed, but currently unneeded due to an implementation bug
elsewhere.

However, if the harness *is* setting things up, it makes it hard (to the
point of impossible) to use the harness running under 1 perl to test code
running under a different perl)

Nicholas Clark