| | 3 | As a first step in the direction of supporting CPAN-style Perl projects we integrated into Padre the use of Module::Starter, The intent is to make it as easy as possible for CPAN authors (and especially for first-time CPAN authors) to have installers that follow all the best practices for distribution installation, but involve as much DWIM (Do What I Mean) as possible when writing them. \\ |
| | 4 | The "bones" of every new module are basically the same: even if it's not your intention to distribute, you should still Build new module frameworks automatically. PBP |
| | 5 | |
| | 6 | * The original, oldest module for installing modules is ExtUtils::`MakeMaker`. |
| | 7 | * the daddy, old, use one of the other's |
| | 8 | |
| | 9 | * Module::Build is pure-perl. This means it does not require a make program to be installed for you to build/install modules. In fact, you don't even need a shell, so even platforms like MacOS (traditional) can use it fairly easily. This is not a problem with recent versions of perl because Module::Build is a core module. |
| | 10 | * pure-perl :) |
| | 11 | |
| | 12 | * Module::Install is a package for writing installers for CPAN (or CPAN-like) distributions that are clean, simple, minimalist, act in a strictly correct manner with ExtUtils::`MakeMaker`, Another very unique feature is auto-install. When the module author enables auto-install for his distribution, Module::Install will search for and install any pre-requisite modules that are not installed when Makefile.PL is executed. |
| | 13 | * used by Catalyst |
| | 14 | |
| | 15 | module-starter will look for a configuration file before reading its command line parameters. The default location is $HOME/.module-starter/config but if the MODULE_STARTER_DIR environment variable is set, module-starter will look for config in that directory. |
| | 16 | \\ |
