in reply to Skipping tests if a module is not available

I wonder what you'd see through both invocation schemes with warn "<$INC{Test/Warn.pm}>\n"; before the pass() call. I suspect the library paths may be different than what you think, if you didn't use -Mblib or some other construct on the perl call.

If that doesn't help, look at what Test::Harness builds up for its arguments to Perl.

Replies are listed 'Best First'.
Re^2: Skipping tests if a module is not available
by Jeffrey Kegler (Hermit) on Oct 31, 2007 at 04:36 UTC
    That explains the mysterious disappearing VERSION problem. The Makefile's library paths and my defaults were different and the former caught an old, development version of of my module, one which didn't set VERSION. I feel so dumb sometimes.

    Thanks.

[reply]
[d/l]

In Section Seekers of Perl Wisdom