From owner-freebsd-ports@freebsd.org Fri Jul 1 19:57:33 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 82055B8F738 for ; Fri, 1 Jul 2016 19:57:33 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4706F2ECE; Fri, 1 Jul 2016 19:57:32 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 96AB628423; Fri, 1 Jul 2016 21:57:29 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8A2F928416; Fri, 1 Jul 2016 21:57:28 +0200 (CEST) Message-ID: <5776CB28.2000709@quip.cz> Date: Fri, 01 Jul 2016 21:57:28 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Don Lewis , freebsd-ports@FreeBSD.org Subject: Re: what to do when base openssl isn't suitable References: <201607011859.u61IxIBt093652@gw.catspoiler.org> In-Reply-To: <201607011859.u61IxIBt093652@gw.catspoiler.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 19:57:33 -0000 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