Oh that comment makes this very confusing then. The CLI doesn't seem to have any way to specify this in the first place? Should we just leave it as false since that's what it's been, and add a…
--apply for nix build
I believe there is a stale CppNix PR to make --apply work for all installables; we should see if that's cherry-pickable
Steps To Reproduce
- Clone git.auxolotl.org/auxolotl/labs via SSH: git clone forgejo@git.auxolotl.org:auxolotl/labs.git
Minor note: clone does not need to be over SSH; we just…
The invocation we typically use to cross compile Lix is:
nix build --impure -E 'let f = builtins.getFlake "git+file:$PWD"; pkgs = import f.inputs.nixpkgs { crossSystem.system =…nix shell and nix develop from
This is, more than anything, showing the tension between the "debug a derivation" use case of nix develop and the "provide a dedicated dev shell" use case.
You know this is a good point,…
This turned out to be a lot easier than we expected! Most of the difficulty was from Meson's docs being bad
nix collect-garbage is kind of slow at deleting paths
This shouldn't have a major effect in that regard — it's not parallelizing, just not blocking deletion by store paths being live from not having been deleted yet, and renames are cheap. But…
This being said, we agree that upgrade-nix really should just be killed, and we should just use the installer for upgrades.
If you're getting a profile conflict with Lix's upgrade-nix, that means that it's using the wrong nix-env (either from CppNix or from a version of Lix that didn't have this fix). Lix's…
I suppose actually we would only need langver for using it without --experimental-features=pipe-operator. In any case, yes please omg!