Build dependencies of packages
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
With the rise of multiple people running nixpkgs-review on PRs in an automated fashion, it might just be better to fold in this feature to ofborg to cut down on the amount of duplicated information.
This isn't to say that nixpkgs-review will be superceded (except for the case where people only check if packages build and not whether they actually function), but that we shouldn't need to rely on contributors to determine if dependent packages built (especially when ofborg already generates a list of affected attrs).
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 by reading ofborg's handling of affected attributes and package builds, then compare the dependency information currently produced by nixpkgs-review. Define how dependent package build results should appear in ofborg and verify that the result avoids duplicated contributor-side checks while preserving nixpkgs-review's functional testing role.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100