Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Jan 2018 09:33:11 +0700
From:      Eugene Grosbein <eugen@grosbein.net>
To:        Matthew Luckie <mjl@luckie.org.nz>, freebsd-ports@freebsd.org
Subject:   Re: using security/openssl in a port
Message-ID:  <5A4EE3E7.5010101@grosbein.net>
In-Reply-To: <d991d276-2672-95cf-86a0-44b334a071d9@luckie.org.nz>
References:  <d991d276-2672-95cf-86a0-44b334a071d9@luckie.org.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
05.01.2018 9:11, Matthew Luckie wrote:

> 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.

https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
https://www.freebsd.org/doc/en/books/porters-handbook/versions-11.html

FreeBSD had openssl-1.0.1 in the base before import of 1.0.2d (1100085),
so use this in the port's Makefile:

.if ${OPSYS} == FreeBSD && ${OSVERSION} < 1100085
# add dependency here
.endif




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5A4EE3E7.5010101>