From owner-freebsd-ports@freebsd.org Fri Jan 5 03:04:04 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 EC748EAA84C for ; Fri, 5 Jan 2018 03:04:04 +0000 (UTC) (envelope-from mjl@luckie.org.nz) Received: from warlock.wand.net.nz (warlock.cms.waikato.ac.nz [IPv6:2001:df0:4:4000::250:15]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A91C570B95 for ; Fri, 5 Jan 2018 03:04:04 +0000 (UTC) (envelope-from mjl@luckie.org.nz) Received: from [130.217.250.39] (helo=sorcerer.cms.waikato.ac.nz) by warlock.wand.net.nz with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eXHzo-0006zU-Uk; Fri, 05 Jan 2018 15:44:41 +1300 Received: from sorcerer.cms.waikato.ac.nz (localhost [127.0.0.1]) by sorcerer.cms.waikato.ac.nz (Postfix) with ESMTP id 84AEA12C07BB; Fri, 5 Jan 2018 15:44:34 +1300 (NZDT) Subject: Re: using security/openssl in a port To: portmaster@BSDforge.com References: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> From: Matthew Luckie Cc: freebsd-ports@freebsd.org Message-ID: <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz> Date: Fri, 5 Jan 2018 15:44:31 +1300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VpgEJ1ExVrLy7i0iGthkOhfWfA4ZHJezS" Received-SPF: none client-ip=130.217.250.39; envelope-from=mjl@luckie.org.nz; helo=sorcerer.cms.waikato.ac.nz X-Spam-Scanned-By: warlock.wand.net.nz (4d8a40d80ed6d03cb975ebc89f40b94e4eb19460) X-Spam-Score: -2.9 (--) 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 03:04:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VpgEJ1ExVrLy7i0iGthkOhfWfA4ZHJezS Content-Type: multipart/mixed; boundary="chmI1oh80JE9fDLCiX3NphnnpF55i2jA5"; protected-headers="v1" From: Matthew Luckie To: portmaster@BSDforge.com Cc: freebsd-ports@freebsd.org Message-ID: <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz> Subject: Re: using security/openssl in a port References: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> In-Reply-To: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> --chmI1oh80JE9fDLCiX3NphnnpF55i2jA5 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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.0.2 = to >> build.=C2=A0 FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onw= ards >> have 1.0.2.=C2=A0 Is there a magic way to have this port depend on por= ts >> openssl for freebsd releases without openssl 1.0.2?=C2=A0 I ran >> >> find /usr/ports -exec grep "security/openssl" {} \; -print >> >> and didn't find anything that I could use as a recipe.=C2=A0 USES =3D = ssl >> doesn't seem to be it either. >> >> Matthew > Hello Matthew, > Have a look at ports/Mk/bsd.port.mk > In there you will find some clues for defining rules for building > for specific (bsd)OS versions -- like >=3DXXXXX, or .if OSREL <=3DXXXXX= X ... > As well as only permitting build/install when the correct version > of security/openssl is found in the systems ports tree. > It's well commented, and should give you some good options to try. > It will also give some good clues to search the ports tree for. Where > you can simply copy someone else's work verbatim. :-) >=20 > You might also try the following alternative for searching; > cd /usr/ports > find . | xargs >=20 > HTH My main worry is that I could not find a single port that apparently depends on security/openssl. 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. Is my worry misplaced? Matthew --chmI1oh80JE9fDLCiX3NphnnpF55i2jA5-- --VpgEJ1ExVrLy7i0iGthkOhfWfA4ZHJezS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHAEARECADAWIQTXPLTkr00GLuDVs20rK4MpIRAAYAUCWk7mkBIcbWpsQGx1Y2tp ZS5vcmcubnoACgkQKyuDKSEQAGDn3ACgnmJTGYnLyCsHSwN89ZkUThQg95AAoJ9g 3CfrP0+Ke08SmNWE/ZnXzBOo =wxcO -----END PGP SIGNATURE----- --VpgEJ1ExVrLy7i0iGthkOhfWfA4ZHJezS--