in reply to installing dependencies
While I think marto has a good suggestion. I like choices (and offering them). I recently had to install a Module for a project I'm working on. It too had external resources that it thought I should/needed to install. It was Lingua-JA-Romanize-Japanese. The build, install session went as follows
and make went in a way I really prefer
# perl ./Makefile.PL
Checking if your kit is complete...
Writing Makefile for Lingua::JA::Romanize::Japanese
Writing MYMETA.yml and MYMETA.json
Choosing n didn't cause a FAIL. As it (the module) still worked w/o those dictionaries. But I just felt this was similar enough to your situation, that it's source might provide some information you might find useful in your current quest.
/usr/local/bin/perl5.12.5 -Ilib -MLingua::JA::Romanize::DictJA -e 'Lin
Updater: Lingua::JA::Romanize::DictJA (0.23)
Loading module: DB_File.pm
Loading module: LWP::UserAgent
Loading module: IO::Zlib
Loading module: Encode.pm
Do you wish to download these files? [y]
¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ƨᴉɥʇ ədoH
UPDATE: A point that might have been missed here; is that this method allows the person installing your module satisfy the dependencies using a different method that maybe their "dist" (OS) can satisfy "natively".
Yes. What say about me, is true.