Skip to content

chore(rumqttc): disable default-features for tokio-rustls#941

Closed
jarhodes314 wants to merge 1 commit intobytebeamio:mainfrom
jarhodes314:chore/remove-aws-dependency
Closed

chore(rumqttc): disable default-features for tokio-rustls#941
jarhodes314 wants to merge 1 commit intobytebeamio:mainfrom
jarhodes314:chore/remove-aws-dependency

Conversation

@jarhodes314
Copy link
Copy Markdown

This disables the default-features of the optional dependency tokio-rustls. I am attempting to build rustls with the ring backend, rather than the newly default aws-lc-sys backend. Currently the unreleased version of rumqttc enables the default features of tokio-rustls, and this is adding an unnecessary dependency on aws-lc-sys.

Type of change

Miscellaneous (related to maintenance)

Checklist:

  • Formatted with cargo fmt
  • Make an entry to CHANGELOG.md if it's relevant to the users of the library. If it's not relevant mention why.

I haven't committed any changes from cargo fmt since this does not affect any rust source. It did appear to make a change in one file that I haven't touched.

I don't believe this needs a changelog entry as it shouldn't really affect downstream use of the crate, other than avoiding bringing in unnecessary dependencies. I believe anybody attempting to use rustls 0.23 in an application will need to call CryptoProvider::install_default, which necessitates a dependency on rustls anyway, which allows them to select the relevant features for their use case.

@jbeyerstedt
Copy link
Copy Markdown
Contributor

I also noticed the sudden introduction of aws-lc-sys in this crate which creates some trouble since it needs quite some more dependencies in the build pipeline (including golang). So would really like to see this merged.

@giridher-art
Copy link
Copy Markdown
Collaborator

@jarhodes314 check #988 , we are currently reviewing this PR. It introduces users to choose their own cryptoprovider along with default feature with aws-lc-rs

@jarhodes314
Copy link
Copy Markdown
Author

@jarhodes314 check #988 , we are currently reviewing this PR. It introduces users to choose their own cryptoprovider along with default feature with aws-lc-rs

@giridher-art that looks like a suitable solution and would at least mean we can depend on the main repository and not a fork.

@giridher-art
Copy link
Copy Markdown
Collaborator

@jarhodes314 if you do need any changes , please let me know ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants