Installing Every NixOS Package
50 points by untrusem
50 points by untrusem
Humorously, running nix-env -i also installs every package. One of the weirder default behaviors I've ever seen in a package management tool.
Finally, nix store delete will no longer realise installables specified on the command-line; previously, nix store delete nixpkgs#hello would download hello only to immediately delete it again. Now, it exits with an error if given an installable that isn’t in the store.
This one from Lix 2.93 is pretty funny, though yours is definitely worse.
Submit it to Nixpkgs. There was an npm package called hoarders a long time ago that had everything in it. and I guess people keep doing it. https://socket.dev/blog/when-everything-becomes-too-much
/run/current-system/sw/bin must be pretty full. I'm surprised using such an obese NixOS does not fail due to overly big env values.
afaik env values don't get larger with this, they'd only get bigger if packages were added via nix shell. installing packages via environment.systemPackages doesn't impact env vars.
[..] changing my shell from Fish to a Go Fish game, so now I can’t even log in!!!
That was a well educating and fun read. Makes me wonder if there was a decent way of enabling a more sophisticated method of avoiding package bin name symlink collisions in nix by namespacing/prefixing them a bit automatically (since packages are pure anyway, so there shouldn't be any dependence on /run/current-system/sw/bin/ls to be present or a particular place beside impure scripts and an interactive shell).