Date: Fri, 5 Jan 2018 15:11:00 +1300 From: Matthew Luckie <mjl@luckie.org.nz> To: freebsd-ports@freebsd.org Subject: using security/openssl in a port Message-ID: <d991d276-2672-95cf-86a0-44b334a071d9@luckie.org.nz>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--GimnVIkOmE1j49buWSr1mcaSNnhafzEtu
Content-Type: multipart/mixed; boundary="d1vjduNpgqz94vIUFKkKVCr8P8R24SzzC";
protected-headers="v1"
From: Matthew Luckie <mjl@luckie.org.nz>
To: freebsd-ports@freebsd.org
Message-ID: <d991d276-2672-95cf-86a0-44b334a071d9@luckie.org.nz>
Subject: using security/openssl in a port
--d1vjduNpgqz94vIUFKkKVCr8P8R24SzzC
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Hi,
I maintain a port that has a new release which requires openssl 1.0.2 to
build. FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards
have 1.0.2. Is there a magic way to have this port depend on ports
openssl for freebsd releases without openssl 1.0.2? I ran
find /usr/ports -exec grep "security/openssl" {} \; -print
and didn't find anything that I could use as a recipe. USES =3D ssl
doesn't seem to be it either.
Matthew
--d1vjduNpgqz94vIUFKkKVCr8P8R24SzzC--
--GimnVIkOmE1j49buWSr1mcaSNnhafzEtu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iHAEARECADAWIQTXPLTkr00GLuDVs20rK4MpIRAAYAUCWk7euBIcbWpsQGx1Y2tp
ZS5vcmcubnoACgkQKyuDKSEQAGBY0ACeJfZIu+FQToptIi+s3jLS/guyqFwAoMzN
dPHoyftecHZYuWp4BGAIRtQ1
=Srt5
-----END PGP SIGNATURE-----
--GimnVIkOmE1j49buWSr1mcaSNnhafzEtu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d991d276-2672-95cf-86a0-44b334a071d9>