How to bootstrap?
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 142
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I'm packaging hypher for Guix (a source-based distro similar to Nix) as part of a larger project to package Typst, and part of our packaging guidelines is to avoid packaging "opaque" binaries if possible. In service of that, I've been trying to find a way to generate the files in the ./tries directory.
The naive answer is to spot the ./tests/generate.rs file and try running cargo test (from a git checkout, as the cargo release is missing ./patterns) but it seems that without the pre-existing binaries, hypher doesn't compile, so generate.rs can't be run. I read in #1 that this choice was made because the process requires human intervention(?), which is understandable, but would you be able to describe your process in detail, so that it can be replicated for Guix?
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
Start with tests/generate.rs and issue #1, then investigate why cargo test from a git checkout depends on the pre-existing binaries and ./patterns. Document the complete process for generating ./tries, including any human intervention, so Guix packaging can reproduce it without opaque binaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100