Re: port:openssl dependency

On Jan 10 15:53:59, dl...@geeklair.net wrote: > On Jan 10, 2018, at 2:49 PM, Jan Stary 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

port:openssl dependency

Dear users and maintainers of qt5 qt55 qt56 qt57 qt58 qt59 fbthrift folly lua-luasec qca wangle scummvm libstrophe profanity qpid-proton snort

lib dependency confusion

On Jan 10 20:49:21, h...@stare.cz wrote: > path:lib/libssl.dylib:openssl > > This means a 'lib/libssl.dylib' needs to be present in $prefix, > and if it's not, it gets installed by installing openssl. > The point of specifying the dependency this way is that > some port other than openssl

Re: port:openssl dependency

On Jan 10 20:49:21, h...@stare.cz wrote: > Could you, the users and maintainers, please test this with your port > and report success or failure here, or preferably at https://github.com/macports/macports-ports/pull/1216 (sorry, I sent before pasting this). Jan

Re: port:openssl dependency

On Wednesday January 10 2018 15:53:59 Daniel J. Luke wrote: >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

Re: port:openssl dependency

On Jan 10, 2018, at 2:49 PM, Jan Stary 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'