]> git.proxmox.com Git - libgit2.git/commit - src/libgit2/libgit2.c
settings: don't hard-code HTTPS capability
authorCarlos Martín Nieto <cmn@dwim.me>
Sat, 17 Dec 2016 14:23:35 +0000 (14:23 +0000)
committerCarlos Martín Nieto <cmn@dwim.me>
Sat, 17 Dec 2016 14:23:35 +0000 (14:23 +0000)
commit061a0ad1f9a33aab07421b51db4194c5fdce2357
tree94f9ff06d7ea79e2a40b7965581fb6492d61e494
parentc5e6ba289266e56b8e7f7c9b463aa7008d4b0258
settings: don't hard-code HTTPS capability

This partially reverts bdec62dce1c17465b7330100ea2f71e63fc411dd which activates
the transport code-paths which allow you to use a custom TLS implementation
without having to have one at build-time.

However the capabilities describe how libgit2 was built, not what it could
potentially support, bring back the ifdefs so we only say we support HTTPS if
libgit2 was itself built with a TLS implementation.
src/settings.c