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 being very judicious in ensuring that nothing in my envoronment 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]
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 bob ball of (OO) string by adding the gui.
In reply to Re^14: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by BrowserUk
in thread ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by yeah
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |