[MacPorts] #64259: mysql8 @8.0.27_4: wrong openssl command used

[MacPorts]

#64259: mysql8 @8.0.27_4: wrong openssl command used
--------------------------+-------------------------
 Reporter:  chrstphrchvz  |      Owner:  herbygillot
     Type:  defect        |     Status:  assigned
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.7.1
 Keywords:                |       Port:  mysql8
--------------------------+-------------------------
 I notice that during configure, this message is output:

 {{{
 -- The openssl command does not support zlib
 }}}

 This is not expected, as the openssl11 port does depend on zlib, and
 `zlib` appears in the output of `openssl-1.1 list -cipher-commands`. I am
 not sure whether this message means the build configuration is different
 or if it is merely informational.

 This is caused by `openssl` being hardcoded in the relevant CMake code
 ([https://github.com/mysql/mysql-
 server/blob/mysql-8.0.27/cmake/ssl.cmake#L238 ssl.cmake]), and the
 `openssl` command in MacPorts is provided by the shim port which in turn
 uses openssl3 (and `zlib` does not appear in the output of `openssl-3 list
 -cipher-commands`); an `openssl` command from the openssl11 port is not
 being used.

 What would be a reasonable approach for having mysql8 use the correct
 `openssl` command? Is it fine to just patch the hardcoded `openssl` to
 `openssl-[openssl::branch]`, or should `[openssl::bin_dir]/openssl` be
 used somehow (e.g. prepend it to the PATH environment variable or an
 appropriate CMake variable, either from the Portfile or the openssl 1.0
 PortGroup)?

-- 
Ticket URL: <https://trac.macports.org/ticket/64259>
MacPorts <https://www.macports.org/>
Ports system for macOS