From owner-freebsd-ports@freebsd.org Fri Jul 1 23:17:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5558B8F7AC for ; Fri, 1 Jul 2016 23:17:47 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7CCD52F45 for ; Fri, 1 Jul 2016 23:17:47 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u61NIpWY004209 for ; Fri, 1 Jul 2016 16:18:57 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> References: <201607012141.u61LfYBN093987@gw.catspoiler.org>, <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> From: "Chris H" Subject: Re: what to do when base openssl isn't suitable Date: Fri, 01 Jul 2016 16:18:57 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-Milter: Spamilter (Reciever: udns.ultimatedns.net; Sender-ip: 127.0.0.1; Sender-helo: ultimatedns.net; ) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 23:17:47 -0000 On Fri, 01 Jul 2016 16:15:12 -0700 "Chris H" wrote > On Fri, 1 Jul 2016 14:41:34 -0700 (PDT) Don Lewis > wrote > > > On 1 Jul, Miroslav Lachman wrote: > > > 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 > > > > USE_OPENSSL is now deprecated and has been replaced by USES=ssl > > > > > .if ${OSVERSION} < 1100000 > > > WITH_OPENSSL_PORT=yes > > > > WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it > > was intended to be used in the port Makefile, only in /etc/make.conf. > > The suggested replacement is to put DEFAULT_VERSIONS+=ssl=openssl in > > /etc/make.conf. > > Wouldn't something along the lines of > > SSL_LIB_DEPENDS= libssl.pc:security/openssl > > get it for you? Ahem... that *should* have read SSL_LIB_DEPENDS= libssl.so:security/openssl Sorry. > > Just a thought, because you asked. ;-) > > --Chris > > > > > > > > > .endif > > > .endif > > > > > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"