what to do when base openssl isn't suitable

Mathieu Arnold mat at FreeBSD.org
Sun Jul 3 16:27:47 UTC 2016

+--On 1 juillet 2016 11:59:18 -0700 Don Lewis <truckman at FreeBSD.org> wrote:
| I've got a port that does not work with base openssl because it looks
| for libssl.pc.  Other than that, I don't think it is picky about what
| flavor of ports ssl is installed.  Because the default version of ssl
| still defaults to base, I don't see a way to get this port to build on
| the cluster, so there is no way to provide binary packages.  That's a
| problem for end users because this port has bunch of huge build
| dependencies.  Thoughts?

Right now, you put int he port's Makefile (it always was wrong to do so,
but so many are doing it...):


This summer, I'll change the default OpenSSL from base to security/openssl,
and at that point, I will remove all the WITH_OPENSSL_PORT for a check with
SSL_DEFAULT (that will get the port ignored if it the wrong SSL is used.)
It needs some work WRT GSSAPI to make sure a sane default is choosen if
building with ports openssl.

And then, in the near future, I'll remove support for base openssl and
gssapi in the ports tree, so that everything is always built with ports.

Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20160703/6c599b1e/attachment.sig>

More information about the freebsd-ports mailing list