Date: Fri, 01 Jul 2016 21:57:28 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Don Lewis <truckman@FreeBSD.org>, freebsd-ports@FreeBSD.org Subject: Re: what to do when base openssl isn't suitable Message-ID: <5776CB28.2000709@quip.cz> In-Reply-To: <201607011859.u61IxIBt093652@gw.catspoiler.org> References: <201607011859.u61IxIBt093652@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Don Lewis wrote on 07/01/2016 20:59:
> I've got a port that does not work with base openssl because it looks
> for libssl.pc. Other than that, I don't think it is picky about what
> flavor of ports ssl is installed. Because the default version of ssl
> still defaults to base, I don't see a way to get this port to build on
> the cluster, so there is no way to provide binary packages. That's a
> problem for end users because this port has bunch of huge build
> dependencies. Thoughts?
There are already packages depending on ports OpenSSL because they need
/usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14)
so I think you can make port depending on ports openssl.
See nginx for example.
.if defined(NGINX_OPENSSL)
USE_OPENSSL= yes
.if ${OSVERSION} < 1100000
WITH_OPENSSL_PORT=yes
.endif
.endif
Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5776CB28.2000709>