If you followed the link I gave above ***[uwinnipeg]***, you would see that the file Crypt-SSLeay.ppd contains:

OpenSSL glue that provides LWP https support Joshua Chamas <josh (at) 
+chamas dot com> install_ssl
[download]

which doesn't look much like a ppd to me?

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>
[download]

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)
[download]

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>
[download]

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

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.

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.

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