Why libsodium source is copied into this repository instead of ref linking with git submodules?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 267
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
No complaints, just asking why libsodium original repository on github is not linked here as a submodule and instead the source files are manually duplicated in this repository. Not that there's anything wrong with it, it's just that a submodule linking might make it easier to manage the codebase. Otherwise, great work with PyNacl 👍🏼
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
The issue names no files, tests, or entry points. First review how libsodium is currently included in the repository and compare that arrangement with a Git submodule; done would require a documented decision about whether changing the dependency-management approach is appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, git, python
- Domain
- build-system, cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100