[MacPorts] #62858: rust declares both a library dependency on path:lib/libssl.dylib:openssl and a build dependency on port:openssl which blocks use of libressl

[MacPorts]

#62858: rust declares both a library dependency on path:lib/libssl.dylib:openssl
and a build dependency on port:openssl which blocks use of libressl
----------------------+--------------------
 Reporter:  bK4gYuRo  |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  Normal    |  Milestone:
Component:  ports     |    Version:
 Keywords:            |       Port:  rust
----------------------+--------------------
 Per email from Ryan Schmidt https://marc.info/?l=macports-
 users&m=162068938923093&w=2:

 {{{
 Often, when someone adds a port to MacPorts that requires openssl or an
 openssl-compatible library like libressl, they write the dependency as
 "port:openssl". This prevents libressl from being used. Currently there
 are a small number of ports in this situation:

 $ port echo depends:'port:openssl($|\s)'
 calendar-contacts-server
 libaes_siv
 netdata
 netdata-dashboard
 ntpsec
 ophcrack
 rizin
 squid4
 sslscan
 rust
 msodbcsql17

 Often, this occurs simply because the contributor was not aware of the
 issue, and switching the dependency to "path:lib/libssl.dylib:openssl" is
 all that's needed to allow libressl to be used if desired. Rarely, there
 are specific reasons why libressl is not compatible with a project; in
 that case, the Portfile should contain a comment line near the
 "port:openssl" dependency that explains why.

 In the case of rust, it declares both a library dependency on
 path:lib/libssl.dylib:openssl and a build dependency on port:openssl,
 which seems like nonsense to me:

 $ port -v deps rust
 Full Name: rust @1.52.1_0
 Build Dependencies:   bin:git:git, path:bin/cmake:cmake, port:cctools,
 port:python39, port:openssl, port:pkgconfig, port:ninja, port:gmake,
 port:ccache
 Library Dependencies: port:libffi, path:lib/libssl.dylib:openssl

 It seems like removing the port:openssl build dependency would be the
 correct thing to do, but I haven't tried to figure out why it's the way it
 is.

 I recommend filing bug reports for any of these ports that do not already
 indicate in their comments a specific reason for incompatibility with
 libressl.
 }}}

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