The long and short of it is a merkle tree of hashed inputs :).
2,440 karma · joined February 23, 2014
The long and short of it is a merkle tree of hashed inputs :).
Note that when PRs merge to the default branch, their cache doesn't come with them. This is how GitHub Action's cache works, as a security measure. However: subsequent rebuilds will, and PRs off the default branch will too.
Our installer also supports some environments that the upstream installer has a harder time with.
The new installer can't _yet_ uninstall a Nix installed from the upstream installer, but our upcoming work on "curing" will bring that.
1. Start learning with https://zero-to-nix.com/
2. Take a look at https://github.com/nix-community/home-manager
Good luck!
No, it can't be used that way on NixOS, but we could put something out that sets up a similar experience on NixOS! Good idea!
We're always looking for good writers, Rust devs, and security folks. People who are in to these things should reach out with their resume: careers@determinate.systems. Note that existing Nix expertise is not required.
On NixOS: I generally agree, though it can be tricky to get that done with NixOS. I bet we can make some inroads there.
Easy questions:
> idempotent
It isn't currently idempotent, but we're working on "curing" which brings some idempotency to it, and allows for "rescuing" installations that aren't working correctly. Curing will also support creating a JSON document for installs that don't already have one.
> profitable company or just a group of Nix believers
We are a for-profit company, and we are a group of Nix believers :).
Bash:
Bash is really hard to get right, and really hard to make fast, and really hard to extend its featureset to more complicated use cases. We could "just" download a bash, but when we're trying to navigate disk encryption and APFS volumes and mounts ... it is quite a lot easier to write and test that code in a "bigger" language.
Also note that it isn't just Bash that we'd need to download, but coreutils and other utilities that Bash is really built on top of. We tried to fix a pretty simple bug last year in the Bash installer, and it took two weeks to validate a relatively straightforward, one line change was valid on all the platforms we target.
You can get almost all the benefits Flakes brings without Flakes using alternatives like niv.
grahamc@scruffy:~/ > echo $NIX_PATH
nixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixos:nixos-config=/etc/nixos/configuration.nix:/nix/var/nix/profiles/per-user/root/channels
you can change the `nixos-config` value to point to somewhere else, or call it like this:`nixos-rebuild -I nixos-config=./configuration.nix`
We think flakes and the new interface are the future, and we're working to bring it home.
However, we decided to wait on those. After all: it only supports rust today, but we're eyeing a future where we support Go + Javascript too. We want Riff to work relatively consistently across these ecosystems.