Traditionally, I would just have C:\perl\binPATH in my variable, but due to version conflicts, I would like to keep different versions of perl in places C:\Perl-versionXY\binand just execute my Perl scripts with a direct call C:\Perl-...\bin\perl.exe theScript.pl.
It actually runs on an automated system, where we already C:\perl\bin\perl.exeinvoke perl scripts for all. (But C:\perl\binalso located in PATH.)
To facilitate the different versions of Perl side by side, I would like to remove the C-perl-bin from PATH to make sure that we never see any side effects from any PATH settings related to Perl.
Is this supposed to work? As for modules that require additional DLL files (eg. LibXML, which require LibXML.dll in the bin perl directory)?
I will use the Strawberry Perl transporter for the side versions. (The readme file mentions some PATH settings, but does not mention what is used for what.)
source
share