4 ms·

That makes sense. Is there a `nix-shell` option that outputs which packages will be compiled from source and which will get a precompiled binary? Something like

• ParetoOptimal 4y ago
  > Something like `nix-shell --dry-run`? Exactly that? Lol :)
  • rrgok 4y ago
    Really? It is not written in the official nix-shell manual https://nixos.org/manual/nix/stable/command-ref/nix-shell.html https://nixos.org/manual/nix/stable/command-ref/nix-shell.ht... I still will try when I get to my macbook. Thank you!
    • ParetoOptimal 4y ago
      I misread that as `nix-build --dry-run`, sorry! You can use nix-build on a shell.nix though i'm pretty sure.
    • SAI_Peregrinus 4y ago
      Just tried it, it does work. Not in the `--help` though.
      • sph 4y ago
        This subthread is exactly why NixOS is getting much traction outside of enthusiasts and people with a lot of patience.
        • rgoulter 4y ago
          Missing a 'not', I think? I think the idea that Nix is difficult to get started with, and undocumented, isn't a surprise to the community. -- These were some of the most repeated points in the community survey. And the topic of the submitted post. That said, I do think Nix has seen a lot of growth over the last year, and I see fewer "nix is so easy" comments.
          • sph 4y ago
            I've been on the sidelines for a while, as I keep hearing that NixOS devs are focusing on the documentation for years now... but to be honest I'm not seeing it yet. Documentation was the thing that turned me off it 4 years ago, and I'm a bit sad to see it's still a big problem even if I keep hearing it's being actively worked on.
• rgoulter 4y ago
  The easiest is to change the default: { avr ? true, arm ? true, teensy ? true }: Change `true` to `false` as needed, only keep the ones you need for you keyboard(s).
  • rrgok 4y ago
    Thank you, I will try again with your suggestions!