[bop-devel] Net::HTTPS::Any test bug / install failure, was: Business::OnlinePayment

Stefan Hornburg (Racke) racke at linuxia.de
Sat Dec 14 02:18:26 PST 2013


On 12/14/2013 12:03 AM, Ivan Kohler wrote:
> On Fri, Dec 13, 2013 at 03:38:14PM +0100, Stefan Hornburg (Racke) wrote:
>> On 02/07/2013 10:28 PM, Ivan Kohler wrote:
>>> On Thu, Feb 07, 2013 at 01:44:00PM +0100, Stefan Hornburg (Racke) wrote:
>>>>
>>>> Ivan, can you please fix the Net::HTTPS::Any bug
>>>> https://rt.cpan.org/Public/Bug/Display.html?id=73363?
>>>>
>>>> This causes install failure of Business::OnlinePayment unless you have both
>>>> SSLeay modules present.
>>>>
>>>> Please let me know if you need assistance.
>>>
>>> I certainly wouldn't refuse a patch, also happy to add you as a co-maint 
>>> for Net::HTTPS::Any
>>>
>>>
>>> For historical perspective, the whole B:OP:HTTPS / Net::HTTPS::Any thing 
>>> was mostly inspiried by Interchange's historical support for either 
>>> module and Mike Heins's reply about it being nice to have
>>> http://www.icdevgroup.org/pipermail/interchange-users/2002-September/026005.html
>>>
>>
>> Yes, please add me as co-maintainer for Net::HTTPS::Any.
> 
> Done.
> 
> FWIW, per above, the whole B:OP:HTTPS / Net::HTTPS::Any was added at 
> Interchange's behest over a decade ago.  From here in 2013, if 
> supporting both SSL modules doesn't make as much sense as it did in 
> 2002, I'm also fine with dumping the whole idea and just picking the 
> current best-practice module for B:OP.
> 

What about requiring LWP::Protocol::https, which depends on IO::Socket::SSL and
finally Net::SSLeay. If that doesn't work for all Perl version, we could pick
Net::SSLeay as SSL module and drop Net::HTTPS::Any.

What do you think?

Regards
         Racke


-- 
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team



More information about the bop-devel mailing list