I'm not sure if this the wanted behavior, correct me if I'm wrong.
As bollard is meant to be used as a library, the current rustls recommendation is trying to fetch the provider from the process and not installing it. To make a comparison, libraris are not supposed to install the tracing subscriber.
But we can still provide a feature (ring for instance), that can be default, that provide installations. That's what the rest of the ecosystem tends to do, see tokio-rustls or hyper-rustls.
Even if the ring feature is enabled, default-feature of
rustls
are still enabled, soaws-lc-rs
provider is also a dependency.I'm not sure if this the wanted behavior, correct me if I'm wrong.
As bollard is meant to be used as a library, the current rustls recommendation is trying to fetch the provider from the process and not installing it. To make a comparison, libraris are not supposed to install the
tracing subscriber
.But we can still provide a feature (
ring
for instance), that can be default, that provide installations. That's what the rest of the ecosystem tends to do, see tokio-rustls or hyper-rustls.