All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

I personally have been annoyed when I go to work on a project and when I try to run the Makefile.PL for the purposed of getting dependencies installed (either via "make installdeps" or cpanm --installdeps.) I get a list of 'pre dependencies', mostly stuff to get Module::Install bootstrapped. I know there's 'config_requires' but this doesn't seem to help with the problem. Typically I solve it with a hack, when I create a new local::lib for a project I preload most of the common Module::Install plugins I use (via Task::BeLike::JJNAPIORK) and just tell contributors to preload that module before doing "perl Makefile.PL", but that feels too much like a hack, although its only a single extra step.
It would be really nice if I could do something like "perl Makefile.PL --list_plugins | cpanm" or even "perl Makefile.PL --bootstrap_author_modules" or similar.
On the other hand, perhaps moving toward using Fatpacker, where the Makefile.PL get generated via an authorside build script, similarly to the way App::cpanminus works, might be a more simply solution (athough that would probably get ugly with plugins like Module::Install::Catalyst, since that's part of the Catalyst::Devel package, which depends on Catalyst, and you'd end up Fatpacking a ton of stuff... Maybe Module::Install::Catalyst could be busted out of Catalyst::Devel?)
I'm not sure which is the best option, but I do know it would be awesome if I could tell someone all they need to do to get started is clone my repo and do "cpanm --installdeps." or similar and it just works without having to do some preparation.