In reply to @antifuchs:asf.computer
amnicolist: you're following the "consuming an overlay" section?

Yes, I saw the stuff about consuming the overlay. That explained how to get the rust-overlay into the pkgs. I think I kind-of get that. The problem came when I wanted to actually install the package. I want to have multiple rust tool chains installed, nightly for some things etc. My understanding fell down when I tried to call something like

  home.packages = with pkgs; [
    rust-bin.stable.latest.default
  ];

In reply to @antifuchs:asf.computer
amnicolist: you're following the "consuming an overlay" section?

Yes, I saw the stuff about consuming the overlay. That explained how to get the rust-overlay into the pkgs. I think I kind-of get that. The problem came when I wanted to actually install the package. I want to have multiple rust tool chains installed, nightly for some things etc. My understanding fell down when I tried to call something like

  home.packages = with pkgs; [
    rust-bin.stable.latest.default
  ];

Nixos would complain that it can't find rust-bin. I don't really get where it comes from in the overlay part so I couldn't reverse engineer the

        # ... things you need to patch ...
      })

Yes, I saw the stuff about consuming the overlay. That explained how to get the rust-overlay into the pkgs. I think I kind-of get that. The problem came when I wanted to actually install the package. I want to have multiple rust tool chains installed, nightly for some things etc. My understanding fell down when I tried to call something like

  home.packages = with pkgs; [
    rust-bin.stable.latest.default
  ];

Nixos would complain that it can't find rust-bin. I don't really get where it comes from in the overlay part so I couldn't reverse engineer the

        # ... things you need to patch ...
      })

Yes, I saw the stuff about consuming the overlay. That explained how to get the rust-overlay into the pkgs. I think I kind-of get that. The problem came when I wanted to actually install the package. I want to have multiple rust tool chains installed, nightly for some things etc. My understanding fell down when I tried to call something like

  home.packages = with pkgs; [
    rust-bin.stable.latest.default
  ];

Nixos would complain that it can't find rust-bin. I don't really get where it comes from in the overlay part so I couldn't reverse engineer the

(final:
        # ... things you need to patch ...
      })

In reply to @amnicolist:matrix.org

Yes, I saw the stuff about consuming the overlay. That explained how to get the rust-overlay into the pkgs. I think I kind-of get that. The problem came when I wanted to actually install the package. I want to have multiple rust tool chains installed, nightly for some things etc. My understanding fell down when I tried to call something like

  home.packages = with pkgs; [
    rust-bin.stable.latest.default
  ];

Nixos would complain that it can't find rust-bin. I don't really get where it comes from in the overlay part so I couldn't reverse engineer the

(final:
        # ... things you need to patch ...
      })

In reply to @ronnypfannschmidt:matrix.org
is there an common way to register new outputs - i'd like to register pre-commit hooks as a flake output in a sane way (new app type)

Jez (he/him) ♾️: system looks correct, is it just impossible to switch out the global one to stable?

❯ nix registry list | grep flake:nixpkgs
system flake:nixpkgs path:/nix/store/splp4lqr6n115q125nhqk2qmg81hsk1r-source?lastModified=1694048570&narHash=sha256-PEQptwFCVaJ+jLFJgrZll2shQ9VI%2f7xVhrCYkJo8iIw=&rev=4f77ea639305f1de0a14d9d41eef83313360638c
global flake:nixpkgs github:NixOS/nixpkgs/nixpkgs-unstable

oh, hah, I have a snippet for this that I stole from somewhere (probably the flakes channel here or on discord):

globalNix = {
      nixpkgs,
      hostName,
      inputs,
    }: let
      lib = nixpkgs.lib;
    in {
      # Setup the registry such that the entries are pinned to the versions we pull in here.
      # That should help with reproducability of disjoint projects & with compile times, too.
      nix.registry =
        (lib.mapAttrs' (name: _v: lib.nameValuePair name {flake = inputs.${name};}) inputs)
        // {
          ${hostName}.flake = self;
          nixpkgs.flake = nixpkgs;
        };
      # Also set the nix path such that pinned versions of stuff is available as channels.
      nix.nixPath =
        (lib.mapAttrsToList (name: _v: "${name}=${inputs.${name}}") inputs)
        ++ [
          "nixpkgs=${nixpkgs}"
          "$HOME/.nix-defexpr/channels"
        ];
    };