|Keep It Simple, Stupid|
Using Module Install to install CGI Appsby skazat (Chaplain)
|on Jan 29, 2007 at 06:43 UTC||Need Help??|
skazat has asked for the wisdom of the Perl Monks concerning the following question:
Can anyone think of an example of using something like Module::Install to use to make a Makefile.PL/Build.pl script to install a program destined to live in a cgi-bin?
I've been continually trying to make my own build system work well and I've basically been struggling with the Bundle:: way of doing things.
Basically, my CGI App relies on a very long list of CPAN modules. Currently, what I do is just add these CPAN modules in the distribution itself. This makes it easy for non-developers to use the program, but to have these modules added in a way that is easy to distribute in this setup is quite a bit of black magic. For example, some modules can only be included if there's a Pure Perl version of the module, some modules are basically hacked versions so they *will* only be Pure Perl versions. It's very messy. And it gives me many headaches.
I'd like to, at the very least have an alternative distribution of my program that doesn't have the CPAN modules installed, but has a install script that'll fetch the correct ones automatically and have these modules installed in the person's site or local perllib. Sounds exactly like what Module::Install is made for.
But, it *does* seem to be Module-specific, and not CGI App specific. Having not gone through the process of trying this all out (it's d/l'ing from CPAN as I type) is there any words of wisdom in using Module::Install for CGI Apps? My App basically contains one perl script, and an army of its own Modules for support.
Anyways, I'll most likely report back on my findings.