From 84ccf3e0b6b231d0cbc3be3c088cb00fa1545c18 Mon Sep 17 00:00:00 2001
From: Michael Smith <michael@spinda.net>
Date: Wed, 26 Jul 2017 13:29:50 -0700
Subject: [PATCH] Control tungstenite/tls with tls feature

Previously tungstenite was always built with its "tls" feature enabled (thus
pulling down native-tls), even when the tls feature wasn't enabled on
tokio-tungstenite. Here we modify Cargo.toml to have tungstenite default to no
active features, then enable the tungstenite/tls feature with
tokio-tungstenite's tls feature. The default configuration remains the same.
---
 Cargo.toml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/Cargo.toml b/Cargo.toml
index baa2e1d..6bf64bd 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -13,15 +13,18 @@ version = "0.2.1"
 [features]
 default = ["connect", "tls"]
 connect = ["tokio-dns-unofficial", "tokio-core", "stream"]
-tls = ["tokio-tls", "native-tls", "stream"]
+tls = ["tokio-tls", "native-tls", "stream", "tungstenite/tls"]
 stream = ["bytes"]
 
 [dependencies]
 futures = "0.1.13"
 tokio-io = "0.1.2"
-tungstenite = "0.2.4"
 url = "1.4.0"
 
+[dependencies.tungstenite]
+version = "0.2.4"
+default-features = false
+
 [dependencies.bytes]
 optional = true
 version = "0.4.3"