Re^14: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003

Could the problem lie with all that additional "gui.*" gunk that you're getting ?

Not as far as I can tell. That's just because I typed "ppm" at a command prompt once and it started the gui. I quit straight away, but I guess it stored some config somewhere in the interim.

I'm almost certain the problems arise because I have two versions of active state installed. 5.8.6 as my main installation, and 5.10.0 whilst I work out how to build all the things I have in the 5.8.6.

I speculate that when you install AS builds, they secrete away some config in the registry somewhere and then go fetch that to decide what build/architecture you have. And even though I'm being very judicious in ensuring that nothing in my environment points to the 5.8.6 installation before running PPM, their script is fetching something from the registry somewhere and making the decision based upon that.

If people would add a bit of trace information, __FILE__ & __LINE__ when issuing error messages, or at least some useful information like say:

ppm install failed: The PPD does not provide code to install for this 
+platform [MSWin32-xyz-pqr]
[download]

tracking down and solving these problems would be so much simpler.

Which is exactly why I stopped using PPM3. And that was before they complicated the existing issues with the great big ball of (OO) string by adding the gui.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^14: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 Download Code

Replies are listed 'Best First'.
Re^15: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by syphilis (Archbishop) on Mar 29, 2008 at 13:59 UTC
I speculate that when you install AS builds, they secrete away some config in the registry I think that's possibly the case with the msi packages, but I don't think you'll strike such an issue if you install from the zip packages. I have 3 ActiveState builds on this box (806, 822 and 1002), all of which were installed from the zip packages, and I don't get any grief from that. I think the msi packages offer an "uninstall" capability - and I think that dictates that the registry is going to be messed with. The zip packages don't have an uninstall capability and don't (afaik) screw with the registry in any way - even if one does let the installation process modify the path (which I don't allow). I personally wouldn't recommend the msi packages under any circumstances. Cheers, Rob	[reply]
Re^16: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 29, 2008 at 14:18 UTC
It is quite possible that I installed 5.8.6 (the first time, a long time ago now) using the msi. I've re-installed it over several times since using the zip to correct various horrors (like early build(s) of 5.8.8), but I doubt I did an uninstall for fear of it removing all the packages I had installed and having to start from scratch. I definitely used the zip for 5.10 (we live and learn :) Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]