damn! the valuable output you’re getting from using “nh” to apply your Nix Flake is absolutely astonishing! ✨🥂
“nh” maintainers have really outdone themselves, definitely a project that deserves all the contributions out there! 👏🫡
i love that #nixflakes are software forever and will still build exactly the same in ten years and that is why i have yet to see a single github repo whose newest commit is older than two years whose flake will successfully build at all
i love that there are two completely separate sets of commands for flakes and non-flakes and that `nix-build` and `nix build` operate on two completely different sets of files, have two completely different sets of command line flags, and don't have feature parity with each other. once you get used to it it's really not confusing at all
i love that `nix-build` makes a pointless http request even if all it's doing is symlinking to a prebuilt package already in /nix/store
i love that there is legitimately no way to make it do an offline build without flakes and even with flakes it will sometimes try to access the internet even if you pass --offline
(3/3)
damn! the valuable output you’re getting from using “nh” to apply your Nix Flake is absolutely astonishing! ✨🥂
“nh” maintainers have really outdone themselves, definitely a project that deserves all the contributions out there! 👏🫡
I found the reason, it's because of this:
https://github.com/NixOS/flake-registry?tab=readme-ov-file#flake-inputs
Looks like it's available for every nix flake users officially and one can implicitly turn it off by configuring the registry options I guess.
But it's suggested to add inputs explicitly, since u might change ur registry later in ur configs in future.
Unexpected learning🤝
Thanks for pointing out this
@justdude
I didn't even notice. LoL.
#nix #flake #flakes #nixflakes #nixregistry #nixconfig #config
you know, i do not think i have ever downloaded a #nix flake from github and had it work without any changes
the people who are completely obsessed with reproducibility and are fond of saying "this software will build and work exactly the same 10 years from now" seem to have forgotten that link rot is a thing
"We're all about those flakes, 'bout those flakes, no channels."
Want to know why? Join our next webinar on Sept 16th, all about #Nix flakes! What they are, why we love them, and how to use them effectively. More info and registration here: https://luma.com/995nq98k
Hope to see you there! #nixos #nixflakes
Find why your devShell, package, etc depends on something interactively!
`nix-tree --derivation .#devShells.x86_64-linux.default`
Is there a way to see why a Flake DevShell depends on a given package easily?
`nix path-info -r .#devShells.x86_64-linux.default` seems obvious but no worky
Particularly, this one sounds:
> Currently, Flake outputs remain an ad-hoc attribute set with mere suggestions rather than rules around what may be exposed and where.
original toot https://en.osm.town/@jakehamilton@hachyderm.io/114491557286210432
How we use Nix with Flakes ❄❄❄❄
https://qeef.srht.site/post/how-we-use-nix-with-flakes/
It looks like we use Nix with flakes since cradle to the grave.
Considering Nix flakes being experimental, that’s scary.
And Nix laungage itself does not help, neither so many conventions and confusions one needs to keep in mind.