Date: Fri, 5 Jan 2018 15:44:31 +1300 From: Matthew Luckie <mjl@luckie.org.nz> To: portmaster@BSDforge.com Cc: freebsd-ports@freebsd.org Subject: Re: using security/openssl in a port Message-ID: <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz> In-Reply-To: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> References: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--VpgEJ1ExVrLy7i0iGthkOhfWfA4ZHJezS
Content-Type: multipart/mixed; boundary="chmI1oh80JE9fDLCiX3NphnnpF55i2jA5";
protected-headers="v1"
From: Matthew Luckie <mjl@luckie.org.nz>
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" <mjl@luckie.org.nz> =
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 <string-to-search-for>
>=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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3677cb37-8cc2-60c0-3e23-55fa507a4465>