libressl: coexistence issue with openssl, openssl3, openssl11

[Zweihorn (@Zweihorn)]

Why was MacPorts starting to install 'openssl3' and 'openssl11' concurrently to an already installed 'libressl' anyway?

AFAIK this behaviour started months ago. IMO during MacPorts 2.7.2 or even earlier.

IMO there should only be 'libressl' installed and other ports have to honor this or have to throw an error.

% port installed | grep ssl
  curl @7.86.0_0+http2+ssl
  curl @7.87.0_0+http2+ssl (active)
  libressl @3.6.1_0 (active)
  net-snmp @5.9.1_1+perl5_34+ssl (active)
  openssl11 @1.1.1s_0 (active)

% port dependents openssl11
python27 depends on openssl11

% port dependents libressl 
curl depends on libressl
libevent depends on libressl
net-snmp depends on libressl
openssh depends on libressl
python310 depends on libressl
python38 depends on libressl
python39 depends on libressl
sane-backends depends on libressl

AFAIK in recent past there was also 'openssl3' installed for 'python27' but vanished some update ago apparently. And I just threw 'openssl' into the basket in the Summary.

Ticket might be linked to:

• comment:ticket:66601:6
• #54744

Hope this helps.

[Zweihorn (@Zweihorn)]

Naturally, one could avoid this by not installing 'libressl' in the first place.

Obviously, that answer would be beside the point here. I intentionally prefer 'libressl' over the other.