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 curl 8.4.0 #1666

Merged
merged 2 commits into from
Mar 22, 2024
Merged

Add curl 8.4.0 #1666

merged 2 commits into from
Mar 22, 2024

Conversation

keith
Copy link
Member

@keith keith commented Mar 22, 2024

@bazel-io
Copy link
Member

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (curl) have been updated in this PR. Please review the changes.

@keith keith mentioned this pull request Mar 22, 2024
@keith keith marked this pull request as ready for review March 22, 2024 00:31
@keith keith enabled auto-merge (squash) March 22, 2024 00:31
@keith keith merged commit 6dd3a6d into main Mar 22, 2024
20 checks passed
@Wyverald Wyverald deleted the ks/add-curl-8.4.0 branch March 22, 2024 18:30
@mmorel-35 mmorel-35 mentioned this pull request Mar 23, 2024
@zaucy
Copy link
Contributor

zaucy commented Mar 25, 2024

it looks like the linux build for this doesn't support SSL (https). Is that right? Would a future patch supporting SSL through boringssl be possible?

@keith
Copy link
Member Author

keith commented Mar 25, 2024

Interesting, considering how this is being used in opentelemetry I'm surprised by that. Does that require boringssl? But regardless I think we should enable things like that through starlark flags for flipping that behavior on / off and just try to pick the most reasonable defaults as best we can

@zaucy
Copy link
Contributor

zaucy commented Mar 25, 2024

Does that require boringssl?

No, but its the only ssl implementation in the bcr. The curl build here https://github.com/googleapis/google-cloud-cpp/blob/main/bazel/curl.BUILD uses boringssl.

I think we should enable things like that through starlark flags for flipping that behavior on / off and just try to pick the most reasonable defaults as best we can

Honestly I'm not sure what the best approach is. I've done config settings here in the past, but I don't know if it was the right call.

I think it would be nice if SSL worked without configuration as a default.

It would be nice if we could declare features at the module level like this:

bazel_dep(name = "curl", version = "8.4.0", features = ["openssl"])

but I don't think something like that exists :/

@fmeum
Copy link
Contributor

fmeum commented Mar 25, 2024

It would be nice if we could declare features at the module level like this

This is something that is coming up in more and more contexts. I think that it could be built in Starlark with no changes to Bazel. I'm planning to look into this soon.

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.

None yet

6 participants