Yes I know that there are workarounds for them to set to use the flake inputs but still… I have set nixpkgs version to 23.11 stable release and that’s good, but if I try to use nix shell, nix profile or even nix-env, they all seem to use the latest master/unstable branch to install the packages by default.

Just want to know why aren’t they just default to use whatever is defined in flake.nix file? <OR> will it be implemented to use it by default in the near future?

Reason as to why I am asking -> This is what I am using to match nix shell and flake inputs, but as you can see they are just workarounds, plus seem to cause more errors and whatnot, plus by ideology one shouldn’t need to specially define it to use some version when everything is already defined.

  • hallettj@leminal.spaceEnglish
    5·
    6 months ago

    It’s possible (and I think advisable) to set your flake nixos config to set the system flake registry to point to the same nixpkgs revision that your flake uses. The nixos-starter-configs standard template has two lines that do this:

    # Opinionated: make flake registry and nix path match flake inputs
registry = lib.mapAttrs (_: flake: {inherit flake;}) flakeInputs;
nixPath = lib.mapAttrsToList (n: _: "${n}=flake:${n}") flakeInputs;

    That actually adds all of your flake inputs to the system flake registry. So for example if in addition to your nixpkgs input you also have an input you named nixpkgs-unstable then can also reference that with stuff like nix shell. For example:

    nix shell nixpkgs#hello nixpkgs-unstable#cowsay
    • Yash Raj@lemmy.worldOPEnglish
      1·
      6 months ago

      Yeah that’s what I am using currently but I was told that by default it follows whatever nixpkgs version is in flake.nix and doing the registry thing is an extra step to make it more systematic. For now I will keep using that.