You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, my custom nixpkgs instance has one big con: running anything has a three-second delay where it says Copying '/nix/store/HASHCONTENTS-nixpkgs-configured. This doesn't happen when I comment out the key line:
I'm unsure as to why this might be. I thought it was some caching thing that I could replicate with cachix, but no, it works without internet. I'm guessing that somehow the default nixpkgs derivation gets special treatment and is always accessible, while our derivation isn't treated as nicely.
@Frontear, if you have any ideas as to why this is, let me know!
The text was updated successfully, but these errors were encountered:
For now, this works as a workaround. Only the unfree registries have the ~3-second delay, so I can only use those when actually needed.
nix.registry=lib.mkForce{nixpkgs.flake=inputs.nixpkgs;nixpkgs-unstable.flake=inputs.nixpkgs-unstable;# Allow running unfree packages with nix3 commands via `nix run unfree#steam`unfree.flake=pkgs.callPackagemyLib.mkUnfreeNixpkgs{path=inputs.nixpkgs;};unfree-unstable.flake=pkgs.callPackagemyLib.mkUnfreeNixpkgs{path=inputs.nixpkgs-unstable;};};
Currently, my custom
nixpkgs
instance has one big con: running anything has a three-second delay where it saysCopying '/nix/store/HASHCONTENTS-nixpkgs-configured
. This doesn't happen when I comment out the key line:Here's a comparison.
The line commented out
Screencast.from.2024-10-18.00-48-54.webm
The line included
Screencast.from.2024-10-18.00-45-34.webm
I'm unsure as to why this might be. I thought it was some caching thing that I could replicate with
cachix
, but no, it works without internet. I'm guessing that somehow the defaultnixpkgs
derivation gets special treatment and is always accessible, while our derivation isn't treated as nicely.@Frontear, if you have any ideas as to why this is, let me know!
The text was updated successfully, but these errors were encountered: