> Both CPAN and CPANPLUS manipulate PERL5LIB for non-install testing.
>
> So you may actually be better off just avoiding automated testing entirely:
>
> exit if $ENV{AUTOMATED_TESTING}
That's an overkill, I think. I also received lots of PASS, which means that
automated testing works more ofthen than not. I only started receiving fails
generated by YACSmoke, and by YACSmoke only. I suppose there are other testing
frameworks, that do their jobs fine, and of course I'm interested in their test
output.
> Though I'd rather try to find a way to get your build system working
> in a way that's more compatible with what CPAN and CPANPLUS expect,
> but since your Makefile.PL/Makefile are so custom, I can see how
> that's more trouble than it's worth.
Yes, me too. However I'm fairly sure that rewriting Prima Makefile.PL in order
to use blib is a large task. Also, if the sole reason to do that is to be
compatible with YACSmoke, and no real productivity gain, I don't know, I guess
it would be much more reasonable to fix YACSmoke to do the proper thing
instead. After all, are modules for testers, or testers for modules?
--
Sincerely,
Dmitry Karasik
