http://www.perlmonks.org?node_id=930541


in reply to automating perl installation

Some common options can be provided as parameters to Configure (e.g. thread support). See INSTALL. INSTALL also mentions:

=head2 Site-wide Policy settings After Configure runs, it stores a number of common site-wide "policy" answers (such as installation directories) in the Policy.sh file. If you want to build perl on another system using the same policy defaults, simply copy the Policy.sh file to the new system's perl build directory, and Configure will use it. This will work even if Policy.sh was generated for another version of Perl, or on a system with a different architecture and/or operating system. However, in such cases, you should review the contents of the file before using it: for example, your new target may not keep its man pages in the same place as the system on which the file was generated. Alternatively, if you wish to change some or all of those policy answers, you should rm -f Policy.sh to ensure that Configure doesn't re-use them. Further information is in the Policy_sh.SH file itself. If the generated Policy.sh file is unsuitable, you may freely edit it to contain any valid shell commands. It will be run just after the platform-specific hints files.

Does that help?