1999 at 12:15:52PM -0800
>Crypt::SSLeay could be upgraded to accomodate recent releases of SSLeay
>& OpenSSL, but Gisle Aas does not seem to be available, and with the
>counsel of [EMAIL PROTECTED] (Andreas J. Koenig), maintainer of
>PAUSE,
>it seems a fine solution to create Crypt::OpenSSL as an extension of
>Crypt::SSLeay, until Gisle Aas might incorporate it into libwww for
>https.
>
>Use of this module then would require the using of it as in "use
>Crypt::OpenSSL"
>before any use of Crypt::SSLeay. Internally, Crypt::OpenSSL would
>hijack
>Crypt::SSLeay's namespace, so LWP/Protocol/https wouldn't know any
>different,
>and would just work. This would not affect the listing in CPAN however,
>as
>there Crypt::SSLeay, and Crypt::OpenSSL would be two separate listing.
>
This sounds great - but I'm not sure how CPAN would handle this. If you
say something like:
cpan> i /Crypt::SSLeay/
then it gives you the distribution that contains the package Crypt::SSLeay.
Then if you say:
cpan> install Crypt::SSLeay
it goes and installs the distribution containing the package 'Crypt::SSLeay'.
So, I guess my question is: how will CPAN know *which* 'Crypt::SSLeay' to
install?
I would think that the namespace would conflict by the indexer that powers CPAN.
Ed
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
