maurice/snix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(snix/docs/TODO): drop Derivation -> Build section

Browse source 
This was most likely meant to refer to `exportReferencesGraph`, not
`fetchClosure`. `fetchClosure` is not used in nixpkgs - I created #127
still.

Issue #44 is extended to mention `ExportedPathInfo`.

Change-Id: Id898cb381db02c83888dc395cf3ab01ae6baf2aa
Reviewed-on: https://cl.snix.dev/c/snix/+/30473
Reviewed-by: Jonas Chevalier <zimbatm@zimbatm.com>
Autosubmit: Florian Klink <flokli@flokli.de>
Tested-by: besadii
This commit is contained in:
Florian Klink 2025-05-04 22:18:12 +03:00 • committed by clbot
parent 0bc0807e24
commit c1331c3d93
1 changed files with 0 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

9
snix/docs/src/TODO.md
View file

@ -70,15 +70,6 @@ Extend the other pages in here. Some ideas on what should be tackled:
is probably still not too clear.
- Absorb the rest of //snix/website into this.
### Derivation -> Build
While we have some support for `structuredAttrs` and `fetchClosure` (at least
enough to calculate output hashes, aka produce identical ATerm), the code
populating the `Build` struct doesn't exist it yet.
Similarly, we also don't properly populate the build environment for
`fetchClosure` yet. (Note there already is `ExportedPathInfo`, so once
`structuredAttrs` is there this should be easy.
### Builders
Once builds are proven to work with real-world builds, and the corner cases
there are ruled out, adding other types of builders might be interesting.