svn commit: r358411 - head/contrib/sendmail/src

Eugene Grosbein eugen at grosbein.net
Mon Mar 2 21:22:04 UTC 2020


03.03.2020 4:13, Jung-uk Kim wrote:

> On 20. 3. 2., Eugene Grosbein wrote:
>> 02.03.2020 21:29, Jung-uk Kim wrote:
>>
>>>>> You can easily repeat the problem using recent ports tree and
>>>>> recent stable/11 and handbook-recommended way.
>>>>
>>>> Mixing base and ports OpenSSLs is a bad idea.  If you decided to
>>>> build some ports with ports OpenSSL for some reason, every ports
>>>> using OpenSSL should be rebuilt with it to avoid this mayhem.
>>>
>>> And vice versa, i.e., every port using OpenSSL should be rebuilt if
>>> you decided to go back to base OpenSSL.
>>
>> One more time: these days it is not possible. There are ports that need new 1.1.1 API
>> and cannot be used with stable/11 using base SSL, there is no choice.
>> That's why base sendmail needs to use new SSL API too.
> 
> I don't understand why you insist on patching Sendmail to use new SSL
> API.  Are you trying to build base Sendmail with ports OpenSSL?  AFAIK,
> there is no way to do that.

I merely try to understand how to unbreak upgrade path for 11.2-STABLE workstations
with stock sendmail and SSL support that also has many ports installed including
ports requiring new openssl API. Because buildworld fails and upgrade is broken.



More information about the svn-src-head mailing list