Discovery: How will distribution of this package work?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
The build process for this library is relatively complex and likely sensitive to different platforms. How can we distribute this crate in a way that it works on each platform? How can we ease compilation as much as possible for downstream users? For our use case specifically, qcs-sdk-rust compiles Python wheels for every major platform, how can we make sure that still works as needed?
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. Start by reviewing the crate's existing build process and the qcs-sdk-rust Python-wheel approach referenced in the discussion; done means an agreed, platform-aware distribution and compilation plan for downstream users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100