On Sat, Nov 14, 2015 at 11:54 AM, Kenneth Wolcott <kennethwolc...@gmail.com> wrote: > On Fri, Nov 13, 2015 at 3:57 PM, <sisyph...@optusnet.com.au> wrote: >> -----Original Message----- From: Kenneth Wolcott >> Sent: Saturday, November 14, 2015 6:11 AM >> To: Perl Beginners >> Subject: Will Strawberry Perl installation cause any conflicts with >> pre-existing Actoive State Perl on W2008 server? >> >>> Can I install Strawberry Perl on a W2008 Server without adversely >>> affecting a currently installed Active State Perl? >> >> >> Yes. >> >> Best way, imo, is to install the "portable" edition of Strawberry Perl, as >> it doesn't make (nor does it need) any alterations to the path. >> To run it, you just double-click on the portableshell.bat that ships with >> it, and use the shell that opens up. >> >> Complete removal of the portable Strawberry Perl installation can be done >> easily at any time - just remove the entire directory in which it's >> installed. >> >> Cheers, >> Rob > > Thank you!
I should have checked with my team prior to installing Strawberry Perl on a production build machine. It would have been more prudent on my part if I had an experimental build machine on which to experiment in order to have some first hand knowledge regarding any conflict between a pre-existing Active State Perl installation followed by a Strawberry Perl installation. Apparently Strawberry Perl did inject itself into the Windows PATH variable resulting in more than one Perl executable being found by the build process that builds the installer. (Not sure if Strawberry Perl was earlier in the path or not, but I suspect that it the fact that there were more than one location of "perl.exe" in the path that was the cause of the problem, not that Strawberry Perl was earlier in the path than Active State). Since this is a non-interactive build process, the popup dialog requesting which Perl should be used was not seen and therefore the build failed. Perhaps our build process should be more resilient :-) Well, lesson learned. I still think I will pursue Strawberry Perl to replace Active State Perl, but I will have to be much more careful in doing so. Thanks, Ken Wolcott -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
