[Catalyst] Suggestions for CatalystX::Installer

[Kieren Diment]

On 12 May 2008, at 13:44, Jonathan Rockway wrote:

>
> Module::ScanDeps
>

needs some configuration || filtering to make sense of it, and warn  
if Makefile.PL looks wrong

> "make catalyst_par"

and improve the documentation here

>
> "make installdeps"
>
> DBICx::Deploy
>
> "make test"
>

Provide some standard configuration for DBIx::Class models, and  
Catalyst::Model::File models so we get a sense of what's required for  
Catalyst::Model::Whatever to support catalystx::installer.  I think  
that View:: logic is probably ususally hard coded into the app, but i  
could be wrong.

Catalyst::Controller::REST for the CRUD stuff required (maybe) -  
remember this originates in a (rejected[1]) google summer of code  
application, so we need to provide learning opportunities as well as  
a final result.

i still want support for GetOpt:: modules as well so that we can do  
all this from the comand line.

The opportunity here is for the whole thing to be done wrong first  
time round so we know what to do for the subsequent iteration.  This  
is a technique that is proven to work in technology development many  
times over [2].

[1] Rejected because google is a python shop and so the perl  
foundation didn't get enough slots, and the enlightened perl  
organisation application was rejected this time round

[2] Although unix looks like it doesn't conform to this, it was the  
licencing that unix got wrong mostly.