Question to #nixos / #nix crowd.
Suppose I have a #flake lock and I want to make sure that the software I wrote will live without maintenance for decades?

I made a system with a lot of arcane dependencies in 2012. But thanks to it being 100% #Erlang, it still works, even though all the libraries that it depend on are not maintained.

It still fetches snapshots from #git, Erlang VM using a specialised tool to install any Erlang VM version and just works!

How do I ensure that the sources that I rely on to evaluate a #nix flake persist?

https://gist.github.com/cognivore/db451216e790dda18e6f787491b00040

cc: @solene

@jonn Fork the source repos of the dependencies and point to them in your flake?

@abnv would forking nixpkgs be enough or do I have to go deeper?

@jonn Depends on how much you trust the dependencies repos to be around after a decade. If you are very paranoid, you can find the closure of your project and fork everything. Nix should be able to build everything from source till the hardware architecture is supported.

@abnv I mean, I trust #nixpkgs repo to be around in a decade, #github to be around in a decade *and* the sources. Is there maybe a way to pin the nixpkgs source tree commit in this line: https://gist.github.com/cognivore/db451216e790dda18e6f787491b00040#file-flake-nix-L3 ?