I have encountered a situation where my module depends on another
module, which depends on a system library (OpenSSL) being at a
reasonably current version.
Failure to be at a reasonably current version still allows my dependency
to install/be satisfied. But my tests (correctly) fail. This gets
h to load my dependencies.
In this case, actually they do. I'm not adding a prereq, just
applying a more stringent test to the environment.
So can/should I delete $WriteMakefileArgs{dynamic_config} & delete
$FallbackPrereqs{dynamic_config}?
Or should there be a &q
CPANTS person, and testing by releasing to cpan is expensive (and
> slightly embarrassing):
>
> * What's the proper magic at "# << "?
> o die?
> o exit non-zero?
> o Unlink Makefile and exit 0? (Is this portabl
