flake-parts instead of flake-utils?
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 762
- Forks
- 105
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
It seems flake-parts is designed more cohesive and minimalistic.
It also seems to have less imports (when following the import chain. The only import is a fork of nixpkgs/lib.
Also i don't need to relearn another pattern it's copies the flake pattern and makes it available at multiple points.
When you use perSystem you get self' and input' with system preselected.
I am not that experienced yet, but getting into flake-parts seemed more intuitive.
(The documentation is a bit lacking)
Please no fights. Just close and block it if it comes to that.
Greetings to all the awesome people :3 :)
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 reviewing the repository's existing flake templates and the issue discussion about flake-parts versus flake-utils. Done would require a maintainer-approved decision on whether and how the templates should change; no specific file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100