git2-rs requires openssl but also requires securetransport
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
Noticed this while trying to setup a new mac using nix instead of .
libgit2 supports both openssl backends and SecureTransport (and will in fact fall back to openssl if it considers SecureTransport too old), and will build just fine with just openssl (or just SecureTransport I assume though I've had a few issues with that).
However git2-rs apparently requires openssl (not entirely clear why) but still forces SecureTransport in build.rs, refusing to build unless both are available, which seems like an unnecessary complication. More so given SecureTransport is apparently deprecated (cf libgit2/libgit2#5914)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading build.rs and the dependency configuration that forces SecureTransport, then compare it with libgit2's HTTPS backend selection described in the issue. Verify whether the crate can build with only OpenSSL available, and add or update coverage so the build no longer requires both backends unnecessarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100