If going with Module::Install you can do this in your Makefile.PL–
use inc::Module::Install; # Define metadata name 'Your-Module'; all_from 'lib/Your/Module.pm'; # Specific dependencies requires 'File::Spec' => '0.80'; test_requires 'Test::More' => '0.42'; recommends 'Text::CSV_XS'=> '0.50'; no_index 'directory' => 'demos'; install_script 'myscript'; WriteAll;
I’m with JavaFan, don't specify a version unless you know you have a reason to do so (feature or bug solved in X.XX for example). CPAN tester failures will probably notify you over time if you missed one that mattered and you can add it then.
Module::ScanDeps might be what you want for getting your dependencies straight but it's probably going to be much more verbose than necessary. Unless you have a monster set of modules, doing it by hand is better. Otherwise a one-liner or two looking for use\swhatever might serve better to get a list of what you're directly loading (and let those package take care of their own dependencies—unless you know they are broken in that regard, which does happen).
In reply to Re: What to specify as minimum dependencies
by Your Mother
in thread What to specify as minimum dependencies
by pokki
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |