oxidecomputer / oxidecomputer/omicron
Consider dropping your fork of pq-sys
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
It seems like omicron uses a fork of pq-sys for several years now. You outline the reasons for that fork here, but these reasons are not longer up to date. I've spend quite some effort in updating the crate and making static linking much easier than before, so it might be meaningful to reevaluate this decision.
(I mostly fill this issue as heads-up, feel free to just close it if you feel it's not relevant)
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 with the fork rationale in pq-sys's README.oxide.md and inspect Omicron's pq-sys dependency references. Confirm whether the current pq-sys makes the fork unnecessary and whether static-linking requirements remain satisfied; done means a maintainer-approved dependency change or a documented decision to retain it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100