One of the difficulties of having multiple installations of perl is that some code runs external scripts using "perl path/to/file param" instead of "$^X path/to/file param"
I though I'd try to change the setup of my CPAN smoker to try to catch these cases. I thought of two strategies: 1) On Windows make sure perl is not in the path and just run smoke testing of CPAN This will cause the problematic modules to fail. At least those that have tests for the relevant code. 2) On Linux it would be harder to eliminate perl from the PATH as the system might need it. So change the PATH so the "perl" that is the first in the path will be some small application that will display an error message and exit. I wrote a small piece of C code to do 2 and now I am running the smoke test. I wonder if anyone else here has done something similar. What are the experiences and what are the pitfalls? regards Gabor
