Port build broken by openssl shim approach?

[chrischavez at gmx.us]

Can someone familiar with the openssl shim port please comment on this issue? —Christopher A. Chavez


>  Prior to `openssl` being a shim port, these symbolic links used to point
>  directly to versioned libraries:
>  {{{
>  ${prefix}/lib/libcrypto.dylib -> libcrypto.1.1.dylib
>  ${prefix}/lib/libssl.dylib -> libssl.1.1.dylib
>  }}}
>  Whereas the shim port now points them to other symbolic links:
>  {{{
>  ${prefix}/lib/libcrypto.dylib
>  ->${prefix}/libexec/openssl11/lib/libcrypto.dylib
>  ${prefix}/lib/libssl.dylib ->${prefix}/libexec/openssl11/lib/libssl.dylib
>  }}}
> 
>  I suspect the issue is that a MySQL CMake script assumes that the
>  `${prefix}/lib/libcrypto.dylib` and `${prefix}/lib/libssl.dylib` symbolic
>  links do not in turn point to other symbolic links. See
>  https://github.com/mysql/mysql-server/blob/beb865a960b9a8a16cf999c323e46c5b0c67f21f/cmake/ssl.cmake#L381-L389
> 
>  Should MacPorts not be pointing `${prefix}/lib/libcrypto.dylib` and
>  `${prefix}/lib/libssl.dylib` to other symbolic links, or should software
>  e.g. MySQL accommodate the approach used by the shim port?
> 
> -- 
> Ticket URL: <https://trac.macports.org/ticket/63641#comment:8>