Re: how to force Build test to load all modules from blib/lib first

Found it! The common module was loading yet another common module that included "use lib ..." that was putting the installed area back in front of blib/lib. I'm beginning to think use lib is evil and PERL5LIB is a much better approach througout.

Comment on Re: how to force Build test to load all modules from blib/lib first

Replies are listed 'Best First'.
Re^2: how to force Build test to load all modules from blib/lib first by Anonymous Monk on Nov 23, 2012 at 00:51 UTC
I'm beginning to think use lib is evil and PERL5LIB is a much better approach througout. No, lib is not evil, lib simply doesn't belong in modules, it belongs in scripts	[reply]
Re^3: how to force Build test to load all modules from blib/lib first (use lib ... is for scripts not modules!) by Anonymous Monk on Nov 23, 2012 at 01:00 UTC
Here is patch for lib.pm, add to sub import `if( ( caller )[1] =~ /\.pm$/ ){ require Carp; Carp::croak( "use lib ... is for scripts not modules!"); }` [download]	[reply] [d/l]