Changes between Version 3 and Version 4 of Ticket #69827, comment 1


Ignore:
Timestamp:
Apr 29, 2024, 11:41:36 PM (3 weeks ago)
Author:
artkiver (グレェ)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #69827, comment 1

    v3 v4  
    55Will:
    66
    7 install OK with %port -v install
     7install OK with %sudo port -v install
    88
    99Defaults to OpenSSL(3) but at least picks up the libretls dependency.
    1010
    11 If LibreSSL or libressl-devel are already installed in MacPorts, it might also work and use the libressl variant if installed with %port -v install +libressl.
     11If LibreSSL or libressl-devel are already installed in MacPorts, it might also work and use the libressl variant if installed with %sudo port -v install +libressl.
    1212
    1313However, there are various caveats:
    … …  
    2323}}}
    2424
    25 Or, cleaning MacPorts entirely via %sudo port -fp uninstall installed and specifying %port -vst install
     25Or, cleaning MacPorts entirely via %sudo port -fp uninstall installed and specifying %sudo port -vst install
    2626
    2727{{{
    … …  
    8888}}}
    8989
    90 Also, I do NOT for the life of me, understand why if I invoke % port -v install +libressl on a clean MacPorts installation it has openssl and openssl3 as dependencies?
     90Also, I do NOT for the life of me, understand why if I invoke % sudo port -v install +libressl on a clean MacPorts installation it has openssl and openssl3 as dependencies? Which, also doesn't seem to pick up the libretls dependency of the openssl variant. My guess is: one of the other dependencies is defaulting to OpenSSL as a dependency? Moreover, this is probably why I don't see this if I already have libressl installed, because whichever port is defaulting to OpenSSL and being flagged as conflicting dependency this way is presumably already handled.
    9191
    9292e.g.