water-sucks / nixos Goto Github PK

There's a community effort to specify the activation interface across configurarions (hm/nixos/darwin/etc): https://github.com/viperML/activation-manager

This is an interesting effort to reduce duplication across configuration systems and we may be one of it's adopters.

nixos-option uses C++ and directly links to libnix* libraries. Implement this command as nixos option by using the libnix* libraries.

It's a good idea to link to the libnix* libraries directly at some point, similar to this tool and nix-collect-garbage, in order to have access to more context without crazy invocation of commands. This will be a potential experiment into how feasible this is with Zig, as we will need to use and/or write C bindings in order to use them reliably from Zig.

https://github.com/nix-community/nixos-anywhere seems to be to the best of my judgment the current best practice in spinning up NixOS.

For a good implementation, my opinion, local should just be the special case of remote (i.e. ssh).

Hence, it might be an interesting feat to synthesize the two and implement nixos install as a reinterpretation of nixos-anywhere that also fully covers the nixos-install.sh use case.

I wonder whether it's feasible, to avoid the --flake mistake of the past.

Let's face it: you either are sold (and use flakes everywhere [you can]) or you aren't and don't touch them [if you can].

So instead, would it be possible to simply have two compile options of nixos? One with and one without flake? -- and avoid unhandy flags.

A thing I felt odd when I used nix was the scattered package import tools that would parse cran, pypi, crates, and such compared to guix where all of those tools are maintained as part of the guix cli itself. Thus it would be nice if this tool would also handle package imports from external package repositories in a similar way.

https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-import.html