From owner-freebsd-ports@freebsd.org Fri Jan 5 02:55:53 2018 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 AB25BEA9DB2 for ; Fri, 5 Jan 2018 02:55:53 +0000 (UTC) (envelope-from portmaster@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 8475B6FF0E for ; Fri, 5 Jan 2018 02:55:53 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w052u1gu096154; Thu, 4 Jan 2018 18:56:07 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz> From: "Chris H" Reply-To: portmaster@BSDforge.com To: "Matthew Luckie" Subject: Re: using security/openssl in a port Date: Thu, 04 Jan 2018 18:56:07 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jan 2018 02:55:53 -0000 On Fri, 5 Jan 2018 15:44:31 +1300 "Matthew Luckie" said > On 01/05/18 15:37, Chris H wrote: > > On Fri, 5 Jan 2018 15:11:00 +1300 "Matthew Luckie" = said > >=20 > >> Hi, > >> > >> I maintain a port that has a new release which requires openssl 1=2E0=2E2 = to > >> build=2E=C2=A0 FreeBSD 10=2E3 and 10=2E4 both have openssl 1=2E0=2E1, and 11 onw= ards > >> have 1=2E0=2E2=2E=C2=A0 Is there a magic way to have this port depend on por= ts > >> openssl for freebsd releases without openssl 1=2E0=2E2?=C2=A0 I ran > >> > >> find /usr/ports -exec grep "security/openssl" {} \; -print > >> > >> and didn't find anything that I could use as a recipe=2E=C2=A0 USES =3D = ssl > >> doesn't seem to be it either=2E > >> > >> Matthew > > Hello Matthew, > > Have a look at ports/Mk/bsd=2Eport=2Emk > > In there you will find some clues for defining rules for building > > for specific (bsd)OS versions -- like >=3DXXXXX, or =2Eif OSREL <=3DXXXXX= X =2E=2E=2E > > As well as only permitting build/install when the correct version > > of security/openssl is found in the systems ports tree=2E > > It's well commented, and should give you some good options to try=2E > > It will also give some good clues to search the ports tree for=2E Where > > you can simply copy someone else's work verbatim=2E :-) > >=20 > > You might also try the following alternative for searching; > > cd /usr/ports > > find =2E | xargs > >=20 > > HTH >=20 > My main worry is that I could not find a single port that apparently > depends on security/openssl=2E I'm worried that its more complicated than > simply declaring a dependency on security/openssl on particular freebsd > versions because other ports that use openssl might link against it > without registering a dependency=2E Is my worry misplaced? Openssl is a PITA=2E You *also* have to consider whether the user is using openssl in $BASE, rather than the ports version=2E There are many variables to consider, and I don't envy you on this=2E :-) If you get something you think might work, feel free to ask about it=2E :-) --Chris >=20 > Matthew