No, I meant something like config.foo = mkMerhe ... As long as you merge directly into the top-level config, you will keep the the infinite recursion as your merged results still could contain the keys you want to merge over.| NixOS Discourse
We can now trivially obtain a Nix data structure that is a tree of the modules that took part in the evaluation of a configuration 🌲 Try it yourself! 💃 First, make sure of course that your Nixpkgs checkout includes the merged PR (which branches it landed in). Now, simply do something like $ nix eval --json '.#nixosConfigurations.termitomyces.graph' > graph.json Or pipe it to a fancy TUI json explorer: $ nix eval --json '.#nixosConfigurations.termitomyces.graph' | nix ru...| NixOS Discourse
Tried to find any kind of resource that breaks down the facts (and not pros/cons, performance comparisons, etc.) how the two modes of installation differ, but no joy: The discussion in the issue Manual: Explain pros and cons of single and multi user installation #2799 doesn’t contain much information. The reddit thread single user vs multi user installation simply suggets that “single-user is semi-deprecated”. (I have only ever used multi-user Nix installs, so I wonder: does single-user...| NixOS Discourse
After the RFC to simplify the package structure, the Nixpkgs Architecture Team is now assembling a working group (WG) to investigate the potential of using a module system for packages in Nixpkgs (see below sections for more details). With this post we’re searching for members of this WG. The WG members will meet regularly to synchronize, while working asynchronously between meetings. As such, WG members are expected to dedicate some time towards this, at least some hours every week. We hav...| NixOS Discourse
Hi, I’m pleased to announce the availability of Nix 2.4. It is available from Download Nix / NixOS | Nix & NixOS. This is the first release in more than two years and is the result of more than 2800 commits from 195 contributors since release 2.3. Highlights Nix’s error messages have been improved a lot. For instance, evaluation errors now point out the location of the error: $ nix build error: undefined variable 'bzip3' at /nix/store/449lv242z0zsgwv95a8124xi11sp419f-source/flake....| NixOS Discourse
