net/haproxy 1.7.0 : libressl support
trtrmitya at gmail.com
Fri Dec 9 10:51:59 UTC 2016
> 9 дек. 2016 г., в 15:44, Luca Pizzamiglio <luca.pizzamiglio at gmail.com> написал(а):
> Hi Dmitry,
> thanks for the suggesstion. There's some discussion on haproxy mailing
> list about how to handle the problem and they're more prone to don't
> support libressl, so my patch could be rejected.
> And, even if my patch is accepted, it will be part of haproxy 1.7.1.
> BTW, I'll fill a PR because the attachments are removed. Then the port
> maintainer (who is in CC) can better decide what to do, if adopt them
> in FreeBSD, if upstrem them, if reject them...
If they accept your change to upstream, i can of course add your patches to ports so 1.7.0 will have it.
If they reject it and refuse to support libressl for some reason, we will not add your patches too, because this is not something FreeBSD-specific.
But i am sure Willy will accept the change if it is properly made (otherwise we don't want it too ;)
> Best regards
>> On Fri, Dec 9, 2016 at 1:02 AM, Dmitry Sivachenko <trtrmitya at gmail.com> wrote:
>>> 8 дек. 2016 г., в 22:51, Luca Pizzamiglio <luca.pizzamiglio at gmail.com> написал(а):
>>> Hi guys,
>>> I had to build haproxy 1.7.0 using openssl and libressl.
>>> libressl support is not really provided, becuase of the
>>> OPENSSL_VERSION_NUMBER issue between those two libraries.
>>> In attachment there're two patches ready to be put in the files
>>> directory and that solve (temporarily) the build issue.
>> First step should be to offer these patches to haproxy maintainers, because this is not FreeBSD-specific problem.
>> Can you please do it?
>>> Best regards
>>> PS I didn't fill a PR because I'm not sure if those patches work in
>>> all situation or with all options, so it's just a help for the
>>> maintainer, but maybe not a solution.
More information about the freebsd-ports