Switch bundled libsodium to a tarball
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 267
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
It would be easier to verify that I haven't modified the bundled libsodium if it was a tarball instead of it being unpacked.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by locating how the bundled libsodium sources are packaged and included, then check the existing build entry points and tests. Done means the dependency is distributed as a verifiable tarball and the normal build and test flow still succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- build-system, cryptography
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100