I'm developing Perl applications at a company. I have a lot of modules. For the web app, I have Model::*
classes which are manipulated from CGI::Application
For my command-line apps, I have a series of Perl classes representing targets for the command-line apps.
Now for the issue
Both my web and command-line apps are designed to "bootstrap" themselves from a single environmental variable, which points to the root of the source code repository.
What this means is that my apps are easily relocatable to anywhere - you just check them out of the source repository and set the environmental variable and you are ready to go.
On the other hand...
My boss thinks that all modules should be built with something like Module::Starter
and be part of a make, make install
Which process do you prefer?
Personally, the make, make install
is just too slow for a rapid edit, run, edit cycle. It would make me 20% slower with no apparent gain.
Also, adding another module would mean editing a MANIFEST file each time.
I simply dont see the Module::Starter paradigm as practical for development of the plethora of modules in a medium-large Perl app... how about you?