doc_faustroll has asked for the wisdom of the Perl Monks concerning the following question:
When the developer runs the script, it will install any needed Perl modules, and then proceed to setup a working dev enviro complete with specific third-party executables and libraries auto-configured and at the ready. The script will use CPAN to install a bundle of my needed modules for the set_up_enviro script. CPAN will bootstrap itself as well.
It looks relatively straightforward for now:
My wisdom question is: What are the use of CPAN in a script current best practices and wisest design decisions for auto bootstrapping of both the Perl enviro and dev enviro? I don't want to tax or try anyone's precious time or patience with how do I do this or that questions which can easily be answered by reading the darn docs. If this intrigues anyone or if anyone has some wisdom or war stories that involve the kind of auto bootstrapping I'm tasking myself with, I'd appreciate your very generously gifted grey matter.
Example areas of question would be: for scripting, CPAN or CPANPLUS? why? any war stories?
canonical example of use of CPAN in a script is:
for $mod (qw(Net::FTP Digest::SHA Data::Dumper)){ my $obj = CPAN::Shell->expand(’Module’,$mod); $obj->install; }
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: CPAN auto_bootstrap
by adamk (Chaplain) on Apr 15, 2006 at 06:59 UTC | |
by Anonymous Monk on Apr 15, 2006 at 16:43 UTC | |
by sgifford (Prior) on Apr 17, 2006 at 17:33 UTC | |
Re: CPAN auto_bootstrap
by barbie (Deacon) on Apr 15, 2006 at 18:14 UTC | |
by doc_faustroll (Scribe) on Apr 16, 2006 at 00:19 UTC |