Yes, that is a can of worms. Sometimes it's easiest to just look at the Changes files of the modules your module depends upon to see if you're using some feature that wasn't available in earlier versions. Then in your Makefile.PL specify a minimum version number for that module which will satisfy your use case.
Dual-lifed modules are tricky too, but the process is similar.
As a last resort you can upload a dev release of your module to CPAN and watch the FAIL reports roll in.
The undertaking of determining what the earliest version of all dependency modules needs to be to support a given module on a given version of Perl is really hard. If you have the time, energy, and capability to do it right, be sure to put it on CPAN. If you don't have the time, energy, and capability to do it right, you are not alone. ;)
Dave
In reply to Re^4: Help with making a Module to reveal supported Perl versions
by davido
in thread Help with making a Module to reveal supported Perl versions
by taint
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |