Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add vendored-openssl feature #324

Merged
merged 2 commits into from
Jan 27, 2023

Conversation

tonowak
Copy link
Collaborator

@tonowak tonowak commented Jan 25, 2023

This PR adds a vendored-openssl default feature that enables vendored-openssl in crates-index dependency.

Because there were some issues in the CI #208, there was a decision to enable by default the vendored-openssl in cargo-semver-checks, but lately there have been some issues with it in some users #272. Now a temporary fix for those users would be to disable default features in cargo-semver-checks (thus disabling the vendored-openssl feature). Because this project is a binary, not a library, we've decided to make vendored-openssl a default feature so that users won't have to separately install openssl on their system.

@@ -41,3 +41,6 @@ toml = "0.5.9"
[dev-dependencies]
assert_cmd = "2.0"
lazy_static = "1.4.0"

[features]
vendored-openssl = ["crates-index/vendored-openssl"]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were you still planning on making this feature be default-enabled to preserve the current behavior, or did you change your mind on it again?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh sorry, I forgot to make a commit for making it a default feature. Gimme a sec.

Copy link
Collaborator Author

@tonowak tonowak Jan 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the reminder. adcf9ef

@tonowak
Copy link
Collaborator Author

tonowak commented Jan 27, 2023

It seems #272 is no longer present in my local machine. I can't reproduce this issue, thus I can't test whether the feature works. :(

@obi1kenobi
Copy link
Owner

Can you just update the top comment in the PR? When we merge, that's what will end up in the commit message, and it currently has incorrect information on whether this feature is on or off by default.

@tonowak
Copy link
Collaborator Author

tonowak commented Jan 27, 2023

Can you just update the top comment in the PR? When we merge, that's what will end up in the commit message, and it currently has incorrect information on whether this feature is on or off by default.

Done.

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.

2 participants