Date: Fri, 1 Jul 2016 14:33:35 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: franco@lastsummer.de Cc: freebsd-ports@FreeBSD.org Subject: Re: what to do when base openssl isn't suitable Message-ID: <201607012133.u61LXZxT093978@gw.catspoiler.org> In-Reply-To: <5E323927-472D-4313-B1CF-ADFADBCF5FB2@lastsummer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 Jul, Franco Fichtner wrote: > Hi Don, > >> On 01.07.2016, at 20:59, Don Lewis <truckman@FreeBSD.org> wrote: >> >> 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 ports, because it won't build with OpenSSL at all. Really nifty reworks happened recently with USES in that regard. Nope, USES=ssl doesn't take an argument. See: <http://docs.freebsd.org/cgi/mid.cgi?a78c3668bb80adaa034dfd298be754c1>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201607012133.u61LXZxT093978>