Date: Fri, 1 Jul 2016 21:56:04 +0200 From: Franco Fichtner <franco@lastsummer.de> To: Don Lewis <truckman@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: what to do when base openssl isn't suitable Message-ID: <5E323927-472D-4313-B1CF-ADFADBCF5FB2@lastsummer.de> 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
Hi Don, > On 01.07.2016, at 20:59, Don Lewis <truckman@FreeBSD.org> wrote: >=20 > 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? Take a look at security/letskencrypt which pins its SSL to LibreSSL from por= ts, because it won't build with OpenSSL at all. Really nifty reworks happene= d recently with USES in that regard. Cheers, Franco
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E323927-472D-4313-B1CF-ADFADBCF5FB2>