Steve_BZ has asked for the wisdom of the Perl Monks concerning the following question:

Hi Guys,

I am currently testing an install script, and I run it several times a day. I'd like to automate: 

$ cpan
cpan> o conf build_requires_install_policy yes
cpan> o conf prerequisites_policy follow
cpan> o conf commit

[download]

Are there any prescribed mantras for this?

Regards

Steve

Replies are listed 'Best First'.
Re: cpan> o conf settings
by ikegami (Patriarch) on Sep 06, 2011 at 22:50 UTC
    o conf commit makes the changes permanent, so I'm assuming something else is changing these settings and also using o conf commit? 
    perl -MCPAN -E'
   CPAN::Shell->o("conf", "build_requires_install_policy", "yes");
   CPAN::Shell->o("conf", "prerequisites_policy", "follow");
   CPAN::Shell->o("conf", "commit");
'

    [download]
[reply]
[d/l]
[select]

      Hi Ikegami,

      Thanks for your post.

      I don't think anything else changes the settings, but I always use the form: 

      $ cpan -i My::Mod

      [download]

      So it comes in and out of cpan. This makes it easier for me to maintain the code. In fact I should probably turn it into a single Perl script, so I can standardise the error handling, and resume from the point of any crashes.

      Thanks again.

      Regards

      Steve

[reply]
[d/l]

        I don't think anything else changes the settings,

        Then you don't need to run any of the commands you specified. o conf commit specifically instructs cpan to remember the changes you made.

[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom