Date: Fri, 5 Jan 2018 20:33:29 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Matthew Luckie <mjl@luckie.org.nz>, portmaster@BSDforge.com Cc: freebsd-ports@freebsd.org Subject: Re: using security/openssl in a port Message-ID: <5A4F7EA9.7050502@grosbein.net> In-Reply-To: <5ea5e276-08da-aec9-ba81-b50ea96bf8c4@luckie.org.nz> References: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz> <5A4EFA61.1030106@grosbein.net> <5ea5e276-08da-aec9-ba81-b50ea96bf8c4@luckie.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xfHpTvModwHpbcSSoRDa8pN0QKxc0H6xi Content-Type: multipart/mixed; boundary="hhbIxlh425Nmdka3VNqKQeAXC3uqFJtOG"; protected-headers="v1" From: Eugene Grosbein <eugen@grosbein.net> To: Matthew Luckie <mjl@luckie.org.nz>, portmaster@BSDforge.com Cc: freebsd-ports@freebsd.org Message-ID: <5A4F7EA9.7050502@grosbein.net> Subject: Re: using security/openssl in a port References: <3bad8f9f1092b028945f9ce7720855e1@udns.ultimatedns.net> <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz> <5A4EFA61.1030106@grosbein.net> <5ea5e276-08da-aec9-ba81-b50ea96bf8c4@luckie.org.nz> In-Reply-To: <5ea5e276-08da-aec9-ba81-b50ea96bf8c4@luckie.org.nz> --hhbIxlh425Nmdka3VNqKQeAXC3uqFJtOG Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 05.01.2018 11:16, Matthew Luckie =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > On 1/5/18 5:09 PM, Eugene Grosbein wrote: >> On 05.01.2018 09:44, Matthew Luckie wrote: >> >>> 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 t= han >>> simply declaring a dependency on security/openssl on particular freeb= sd >>> versions because other ports that use openssl might link against it >>> without registering a dependency. Is my worry misplaced? >> >> Why don't you read the Porter's Handbook? It has answers to all your q= uestions: >> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/use= s-ssl.html >=20 > I already said that I considered USES =3D ssl and that it didn't seem t= o > address my concerns. Can you please point me at a port that depends on= > OpenSSL from ports using USES =3D ssl (or whatever this page of the > porters handbook is trying to tell me to do). For example, net/vtun has this: =2Einclude <bsd.port.pre.mk> =2Eif ${SSL_DEFAULT:Mopenssl-devel} BROKEN=3D Does not build with openssl-devel =2Eendif =2Einclude <bsd.port.post.mk> That is, it stops build if user has specified SSL_DEFAULT=3Dopenssl-devel= =2E You need to stop build if FreeBSD version is old and user has NOT specifi= ed SSL_DEFAULT=3Dopenssl (instead of SSL_DEFAULT=3Dbase) to build your port = with security/openssl. --hhbIxlh425Nmdka3VNqKQeAXC3uqFJtOG-- --xfHpTvModwHpbcSSoRDa8pN0QKxc0H6xi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJaT361AAoJELDNGvImmIsoChYH/jBHAjnqJi37QOpYPjBb+g7M 0OnAFxY3pwZZ7OX0+QFy+zW8acLVwRRyWJG1gItgr0HBEMoLJrcPtTkWHMxzIDvT emWmvSetR1AgcgFQ5CLk4VXL8yegYVw8VhzAx2pO6Yd5ASd5MWJeThXWy8qmyRNP GQ7NHu4CD0YxYiqW2o9NbJsHl2pvp8dCXxg4kEL/KF/bUYQmu4/2XapJroABtp4/ 723cTqhm+7ISM2N2K2LwAymhJC7Pp/MIvpUA88HOBqOW2yrtvVb0UEua5X/TyXMM W9d3B8QsgU5FPH+v50HKvXJMmGorigDtBg3/l51s0CDgqsaT+8RxwsZZdh+Kg8Y= =2RXo -----END PGP SIGNATURE----- --xfHpTvModwHpbcSSoRDa8pN0QKxc0H6xi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5A4F7EA9.7050502>