in reply to Re^9: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
in thread ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003

which doesn't look much like a ppd to me

When I click on that link I get:
<?xml version="1.0" encoding="UTF-8" ?> - <SOFTPKG NAME="Crypt-SSLeay" VERSION="0,53,0,0"> <TITLE>Crypt-SSLeay</TITLE> <ABSTRACT>OpenSSL glue that provides LWP https support</ABSTRACT> <AUTHOR>Joshua Chamas <josh (at) chamas dot com></AUTHOR> - <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8" /> <CODEBASE HREF="http://theoryx5.uwinnipeg.ca/ppms/x86/Crypt-SSLeay.t +ar.gz" /> <INSTALL EXEC="PPM_PERL" HREF="http://theoryx5.uwinnipeg.ca/ppms/scr +ipts/install_ssl">install_ssl</INSTALL> <PROVIDE NAME="Crypt::SSLeay" VERSION="0.51" /> <PROVIDE NAME="Crypt::SSLeay::Conn" /> <PROVIDE NAME="Crypt::SSLeay::CTX" /> <PROVIDE NAME="Crypt::SSLeay::Err" /> <PROVIDE NAME="Crypt::SSLeay::MainContext" /> <PROVIDE NAME="Crypt::SSLeay::X509" /> <PROVIDE NAME="Net::SSL" VERSION="2.77" /> </IMPLEMENTATION> </SOFTPKG>
Sometimes I've found that you have to "View Source" to see what's *really* there.

For example, when I go to the bribes ppd I get:
OpenSSL support for LWP David Landgren (david@landgren.net)
But when I "View Source" I see:
<SOFTPKG NAME="Crypt-SSLeay" VERSION="0,57,0,0"> <TITLE>Crypt-SSLeay</TITLE> <ABSTRACT>OpenSSL support for LWP</ABSTRACT> <AUTHOR>David Landgren (david@landgren.net)</AUTHOR> <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread" /> <CODEBASE HREF="Crypt-SSLeay-0.57-PPM56.tar.gz" /> </IMPLEMENTATION> <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8" /> <CODEBASE HREF="Crypt-SSLeay-0.57-PPM58.tar.gz" /> </IMPLEMENTATION> <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.10" /> <CODEBASE HREF="Crypt-SSLeay-0.57-PPM510.tar.gz" /> </IMPLEMENTATION> </SOFTPKG>
In both cases the ppd is valid.
Incidentally, I'm equally puzzled as to why you get that error you reported when you try to install the bribes ppm of Crypt-SSLeay. For me, ppm install http://www.bribes.org/perl/ppm/Crypt-SSLeay.ppd works fine on 5.10.

Cheers,
Rob

Replies are listed 'Best First'.
Re^11: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by Not_a_Number (Prior) on Mar 29, 2008 at 12:20 UTC

    For the record, I just tried the same command, i.e.

    ppm install http://www.bribes.org/perl/ppm/Crypt-SSLeay.ppd

    and it worked fine on 5.10 for me too.

      Aaaaargh! So what am I doing wrong???

      c:\Perl510\bin>ppm install http://www.bribes.org/perl/ppm/Crypt-SSLeay +.ppd ppm install failed: The PPD does not provide code to install for this +platform c:\Perl510\bin>lwp-request http://www.bribes.org/perl/ppm/Crypt-SSLeay +.ppd <SOFTPKG NAME="Crypt-SSLeay" VERSION="0,57,0,0"> <TITLE>Crypt-SSLeay</TITLE> <ABSTRACT>OpenSSL support for LWP</ABSTRACT> <AUTHOR>David Landgren (david@landgren.net)</AUTHOR> <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread" /> <CODEBASE HREF="Crypt-SSLeay-0.57-PPM56.tar.gz" /> </IMPLEMENTATION> <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8" /> <CODEBASE HREF="Crypt-SSLeay-0.57-PPM58.tar.gz" /> </IMPLEMENTATION> <IMPLEMENTATION> <OS NAME="MSWin32" /> <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.10" /> <CODEBASE HREF="Crypt-SSLeay-0.57-PPM510.tar.gz" /> </IMPLEMENTATION> </SOFTPKG> c:\Perl510\bin>ppm-shell ppm 4.01 Copyright (C) 2007 ActiveState Software Inc. All rights reserved. ppm> config list arch = MSWin32-x86-multi-thread-5.10 gui.filter = gui.filter.fields = name gui.filter.type = all gui.geometry = 568x535+364+272 gui.install_area = site gui.view.abstract = 1 gui.view.area = 1 gui.view.author = 0 gui.view.available = 1 gui.view.installed = 1 gui.view.name = 1 gui.view.repo = 1 gui.view.sortcolumn = name gui.view.sortorder = -increasing gui.view.statusbar = 1 gui.view.toolbar = 1 ppm> quit

      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.
        It installed successfully for me too on Windows XP ActivePerl 5.8 for what its worth!

        UPDATE

        But not in 5.10
        So what am I doing wrong???

        Nothing that I can see. I'm seeing the same ppd file as you, and I've got the same version of PPM (4.01).

        One difference is that when I run that config list command in the ppm shell, my output is simply arch = MSWin32-x86-multi-thread-5.10 . Could the problem lie with all that additional "gui.*" gunk that you're getting ?

        (I, too, like to avoid getting closely involved with PPM.)

        Cheers,
        Rob

        Well I get the same output as you from the lwp-request, but a slightly different result from ppm config list:

        arch = MSWin32-x86-multi-thread-5.10 gui.filter = gui.filter.fields = name abstract gui.filter.type = installed gui.geometry = 568x535+154+154 gui.install_area = site gui.view.abstract = 1 gui.view.area = 1 gui.view.author = 0 gui.view.available = 1 gui.view.installed = 1 gui.view.name = 1 gui.view.repo = 0 gui.view.sortcolumn = name gui.view.sortorder = -increasing gui.view.statusbar = 1 gui.view.toolbar = 1

        But whether that helps or not is way over my head, I'm afraid. :-(

        Update:

        Hey, I just reread the OP title: "...errors on Windows 2003". Like Gavin, I'm using XP. Is that it?

        ppm had that bug for 5.8
Re^11: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by BrowserUk (Patriarch) on Mar 29, 2008 at 12:08 UTC

    I see the exact opposite of you when clicking those links. uwinipeg require a view source, bribes doesn't. The "problem" with the uwinnipeg would just be the absence of a 5.10 implementation then.

    As for why the bribes works for you and not me? I really have no idea. As I showed, the architectural strings match, so what else could it be? PPM internals have gotten more and more complex and harder to follow. It's simply quicker and easier to build stuff manually.

    But that fails when you try things like Devel::Cover. Sure, when 5.12 comes out in what, say 3 years from now?, p5p may have "adopted" it and exported those symbols on a "no warranties" basis, just as they have Devel::Alias. But then there will be another package that won't build for similar reasons and we'll have to wait another 3 years...?


    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.
      The "problem" with the uwinnipeg would just be the absence of a 5.10 implementation then

      There's a perfectly valid (afaik) uwinnipeg 5.10 implementation here

      Cheers,
      Rob