Bug 208075

Summary: devel/efl still should not require OpenSSL from ports, GnuTLS should be an option
Product: Ports & Packages Reporter: Mikhail T. <mi>
Component: Individual Port(s)Assignee: freebsd-enlightenment mailing list <enlightenment>
Status: Open ---    
Severity: Affects Only Me CC: christopherpetrik335, gblach, w.schwarzenfeld
Priority: --- Keywords: patch-ready
Version: LatestFlags: bugzilla: maintainer-feedback? (enlightenment)
Hardware: Any   
OS: Any   
Attachments:
Description Flags
Do not require OpenSSL from port, allow use of GnuTLS none

Description Mikhail T. 2016-03-16 23:19:55 UTC
Created attachment 168309 [details]
Do not require OpenSSL from port, allow use of GnuTLS

The problem once solved under Bug #195532 reared its head again with the recent upgrade of the port.

The proposed patch once again removes the gratuitous requirement, while also adding the GNUTLS option.
Comment 1 Grzegorz Blach freebsd_committer 2016-03-17 15:42:40 UTC
On older FreeBSD releases (but still supported) base OpenSSL is too old to work with EFL, in this case WITH_OPENSSL_PORT=yes is required.

OPTIONS_RADIO allows to not select any choice, so NOSSL is redundant.
Also case without any selected choice isn't handled by your patch.
Comment 2 Walter Schwarzenfeld freebsd_triage 2018-01-13 06:16:58 UTC
Is it solved or overcome by events?
Comment 3 Chris Petrik 2018-03-13 23:27:30 UTC
I don't see where enlightenment actively requires OpenSSL from ports? Will Uses SSL not detect base/ports ?
Comment 4 Chris Petrik 2018-03-13 23:29:55 UTC
The patch for gnutls should be communicated with the head dev, so we don't have lame patches such as patch-gnutls with 4 lines :).