Vendoring dependencies in released sources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 748
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Greetings,
I'd like to suggest adding a way to provide a source archive which includes vendored dependencies for all future releases.
This can be helpful for Linux package maintainers when trying to build a distro-specific package from source, especially if the build happens in an offline environment.
If this is deemed useful, I've already implemented it on a test branch using a dedicated Github workflow and can submit a PR.
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
Review the repository's release configuration and the dedicated GitHub workflow proposed in the issue. Confirm how future source archives are generated and how Rust dependencies can be included for offline distro builds. Done means releases provide a source archive with vendored dependencies without disrupting existing release artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100