Changes between Version 1 and Version 2 of Ticket #69490, comment 3


Ignore:
Timestamp:
Apr 25, 2024, 8:23:06 PM (7 months ago)
Author:
artkiver (グレェ)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #69490, comment 3

    v1 v2  
    99In that instance, I could force port:libressl instead of using the dylib approach which had been functional previously I guess?
    1010
    11 I also tried to crib from the approach I used in the rpki-client Portfile, which attempts to be a little bit smarter with looking into what TLS library MacPorts has installed already and if using OpenSSL, to also install libretls to provide libtls (which is where the GitHub Action CI appears to be breaking with the got 0.98.2 PR I submitted) but when I tried that approach locally, for reasons that are a bit beyond me, MacPorts was still trying to install OpenSSL as a dependency, even when I was explicitly using the +libressl variant; which isn't how that should be functioning, at all.
     11I also tried to crib from the approach I used in the rpki-client Portfile, which attempts to be a little bit smarter with looking into what TLS library MacPorts has installed already and if using OpenSSL, to also install libretls to provide libtls (which is where the GitHub Action CI appears to be breaking with the got 0.98.2 PR I submitted) but when I tried that approach locally, for reasons that are a bit beyond me, MacPorts was still trying to install OpenSSL as a dependency, even when I was explicitly using the +libressl variant; which isn't how that should be functioning, or at least not how it previously functioned, at all.