using security/openssl in a port

[Mathieu Arnold]

Le 05/01/2018 à 03:11, Matthew Luckie a écrit :
> 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 = ssl
> doesn't seem to be it either.


You NEVER forcefully depend on security/openssl directly. You USES=ssl,
and you use whatever default is available.  So, in your case, you need
something like this:


.include <bsd.port.options.mk>

.if ${OSVERSION} < 1100085
BROKEN_SSL=   base
BROKEN_SSL_REASON= Needs OpenSSL 1.0.2+
.endif


-- 
Mathieu Arnold


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20180105/0ceeb63e/attachment.sig>