The downside is that then everybody gets asked which curl package to use
when it gets installed as a dependency.. and I bet many people will choose
"full" when they don't need it (and unnecessarily pull in a bunch of other
libraries to the address space, and maybe also submit ports with a bunch of
junk WANTLIBs). At least using "gssapi" means people are slightly less
likely to choose it!
On 10 November 2016 06:40:17 Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote:
(The heimdal krb5-config diff is in.)
Jiri B <ji...@devio.us> writes:
On Tue, Nov 01, 2016 at 03:52:00PM -0400, Jiri B wrote:
With the path and my original path I was able to build curl with
gssapi and ssl:
$ curl -V
curl 7.50.3 (x86_64-unknown-openbsd6.0) libcurl/7.50.3 LibreSSL/2.0.0
zlib/1.2.3 libidn/1.33 nghttp2/1.16.0
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp
smb smbs smtp smtps telnet tftp
Features: IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz
HTTP2 UnixSockets
Although I still have some issues to tested in our krb env.
It works! I tried this:
[...]
Will this go in?
What about something like FLAVOR=full, which would also enable support
for ldap and other features? I can cook a diff if naddy agrees.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
