Attendees: @edolstra @roberth @L-as
Reviews
- (RFC) Doc comments
-
Doc comments by roberth · Pull Request #11072 · NixOS/nix · GitHub
- Reviewed by @edolstra
- Finished and merged
-
Doc comments by roberth · Pull Request #11072 · NixOS/nix · GitHub
Attendees: @edolstra @roberth @ericson2314 @tomberek @L-as
Discussion
What is the state of fetchTree stabilisation?
- Three areas that need improvements
- Internal architecture is still a risk (no structs that inform what’s going on)
- @ericson2314: If I can make good progress on
- Returning path values? (Lazy `fetchTree` `outPath` path values by roberth · Pull Request #10252 · NixOS/nix · GitHub)
- @ericson2314: This is my number one blocker.
- @ericson2314 & @roberth, since Roberth is busy for a while, it would be really good if @edolstra could take this PR (itself taking from his lazy trees branch) and finish it off.
- Individual fetchers. We’d like the stable feature to be useful, not a skeleton of a primop that needs more features enabled to be useful.
- Git core: work tree should be unsmudged. Possible solutions
- Preferably: just smudge them. This is whatgit commit
does anyway and what we should reproduce.
- Shortcut to stabilisation: disallow smudging altogether in worktree (ie using gitattributes support in libgit2)
- or another shortcut: filter out smudged files by default? - Git features:
- actual LFS support: nice to have
- subdirectory-only fetching (“subtree”?): also nice to have - Tarball: single-file bug and tarballs with multiple files in the root (seems basic but perhaps not essential?)
- GitHub: behave more like
git
? Fetch tree-based archives- probably didn’t have smudging, but
- changing this gets rid of the export-subst weirdness that causes hashes to change when going from local dev to
inputs
- makes it so that git-based fetching can be used as a fallback, to solve the rate limiting issue
- Git core: work tree should be unsmudged. Possible solutions
- Internal architecture is still a risk (no structs that inform what’s going on)
Hacking session
Attendees: @edolstra @roberth @ericson2314 @tomberek @fzakaria @L-as
Config work questions
-
More structured settings in nix store URLs are needed for further config system +
lib{store,expr,util}
-
(And BTW, finishing this )
-
More structured settings in nix store URLs · Issue #11106 · NixOS/nix · GitHub