On Jan 10 15:53:59, dl...@geeklair.net wrote:
> On Jan 10, 2018, at 2:49 PM, Jan Stary <h...@stare.cz> wrote:
> > these ports specify a hard dependency on openssl with "port:openssl".
> 
> is libressl now ABI compatible with openssl? IIRC some ports moved from path 
> back to port style dependencies on openssl since libressl was only 'source' 
> compatible and so if you have a path-style dependency and users get things 
> from the buildbot (that were built against openssl) they get non-working ports

If you have libressl installed and install e.g. lynx with
'port install lynx', it downloads the precompiled lynx,
installs  it, and reports it as broken, offering to rebuild.
If you agree to rebuild, it recompiles against the installed libressl.

How exactly is the decision made about lynx being 'broken'
in this situation?

        Jan

Reply via email to