comment on

We're trying to deploy a Perl environment out to numerous test platforms that will be running Windows/Linux/Solaris and Dos. The 2 real OSes (And Windows) will use multiple architectures to complicate things.

Windows is currently the long pole since it doesn't come with a compiler and mingw/dmake/etc aren't working real well for us. PPM from activestate doesn't have all the modules that cpan does (IE not seeing HTTP::Daemon)

What suggestions does everyone have to this problem? IE how would you deploy perl and numerous cpan modules to windows x86/x86_64/ia64, Linux x86/x86_64/ia64/ppc, Solaris sparc/x86/x86_64 and Dos? Dos can be left out since its a special case.

We're also wanting an automated install so testers do not need to configure much of anything other than installing Perl.

In reply to Suggestions on Deploying Perl Test Environment by diabelek

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.


"be consistent"
	PerlMonks