> I have found that there is documentation indicating the automation of > modules: > perl -MCPAN -e 'install Bundle::myBundle' > where myBundle is basically a pod file with =head1 CONTENTS and then a
> list of the modules to install. > > I have seen some documentation using the interactive CPAN shell that > indicates that using o conf <scalar option> <value> allows the setting > of these particular values. I have not found documentation on > scripting out the parameters to the Config.pm file. I was considering > echoing the values out to the file, but I would prefer to send perl > commands so as not to mess up the format or syntax, i.e. perl [some > switch(s)] [some arguments]. > > thanks, > > Michael > > p.s. Sorry about the perl Ok, let's back up a bit. I am assuming that Perl is installed, CPAN is installed in at least its stock form. So my first question, why use a shell script instead of a Perl script? Second question would be how many of the values are changing based on the actual location of install? In other words, can it be enough to just install the same base config file? Ah, now to the beauty of open source, it appears after a cursory cracking open of CPAN.pm (we can, you know, isn't it grand!) when storing a configuration using 'o conf commit' CPAN simply calls the 'CPAN::Config->commit' method. CPAN::Config is just a hash of configuration options (well actually an object), and 'commit' uses ExtUtils::MakeMaker::neatvalue to actually store the values. There are also a number of other neat methods for manipulating CPAN configs in CPAN::Config, such as 'edit' and 'load', presumably everything one needs to automate the process. Under 'CONFIGURATION' in perldoc CPAN is a list of the properties that you may configure (or just crack open a Config.pm that was previously made). Thoughts? http://danconia.org Okay. - Perl is installed. - Nothing has been done to the default install (I have not installed anything nor even gone into the shell). I am assuming that this means that CPAN is in a default state as I have that directory in the installation directory. - I am not opposed to using a perl script as long as I can use it in it's default installed state. - Not being familiar with perl, I did look at the FirstTime script and became slightly overwhelmed and therefore joined the list. - Is it possible to drop a previously created Config.pm file into place without error or repercussion? - Are you suggesting running or revamping the Config script to suit my needs? Thank you for your patience and instruction. I am learning a lot. Michael -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
