comment on

Just create CPAN/Config.pm yourself and put it in a place where it loads before any other CPAN::Config. As long as Perl finds it and it's not missing configuration data, CPAN won't start its interactive configuration. The CPAN::HandleConfig::load method is your map to doing it yourself and avoiding the interactive configuration.

The CPAN::Config module itself is just an anonymous hash, so you don't have to do that much work to create it yourself. Create the hash with the local values and dump it:

$CPAN::Config = {
  'build_cache' => q[10],
  'build_dir' => q[/Users/brian/.cpan/build],
  'cache_metadata' => q[1],
  'cpan_home' => q[/Users/brian/.cpan],
  'dontload_hash' => {  },
  'ftp' => q[/usr/bin/ftp],
  'ftp_proxy' => q[],
  'getcwd' => q[cwd],
....
  };
1;
[download]

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review

In reply to Re: scripted cpan configuration by brian_d_foy
in thread scripted cpan configuration by tphyahoo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks