Committer needed for PR 208029

Jim Ohlstein jim at
Wed Apr 6 14:06:44 UTC 2016


On 4/6/16 12:44 AM, Kurt Jaeger wrote:
> Hi!
>> Actually, I just noticed (when compiling the port), that the Makefile now says:
> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
> now as IGNORE with a message explaining how to do it for 9.x.

This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there 
for just this purpose and is used in many ports. There's no reason some 
binaries can't be linked to one version of OpenSSL and others to 
another, so long as they aren't expected to work as one (I'd imagine a 
dynamically loaded module that is linked to a different library might 
cause a problem). That is the reason that ports contains a more current 
version than base. This is from the ports/www directory:

#  grep WITH_OPENSSL_PORT */Makefile
aws/Makefile:WITH_OPENSSL_PORT= yes
drood/Makefile:WITH_OPENSSL_PORT=	yes
h2o/Makefile:WITH_OPENSSL_PORT=	no
h2o/Makefile:WITH_OPENSSL_PORT=	yes
mod_tsa/Makefile:WITH_OPENSSL_PORT=	yes
nginx-devel/Makefile:WITH_OPENSSL_PORT=	yes
nginx-devel/Makefile:WITH_OPENSSL_PORT=	yes
nginx/Makefile:WITH_OPENSSL_PORT=	yes
nginx/Makefile:WITH_OPENSSL_PORT=	yes
owncloud/Makefile:WITH_OPENSSL_PORT=	yes
spdylay/Makefile:.if ${OSVERSION} < 1000000 && !defined(WITH_OPENSSL_PORT)
tengine/Makefile:WITH_OPENSSL_PORT=	yes
tomcat-native/Makefile:WITH_OPENSSL_PORT=	yes

I'm sure there are dozens of others.

Forcing users who want to use this port to use OpenSSL from ports for 
ALL ports is overkill.

Think about official packages. Are ALL packages built against OpenSSL 
from ports, or only those that need them? It's the latter, of course. 
Are they incompatible in production? No.

Jim Ohlstein

"Never argue with a fool, onlookers may not be able to tell the 
difference." - Mark Twain

More information about the freebsd-ports mailing list