Question to / crowd.
Suppose I have a 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% , it still works, even though all the libraries that it depend on are not maintained.

It still fetches snapshots from , 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 flake persist?

gist.github.com/cognivore/db45

cc: @solene

@jonn @solene That's assuming Flakes doesn't change too much as the feature stabilizes. Changes, if any, will be superficial syntax.

I know @matthewcroughan has a source copying solution called marsnix, or is that too much geared towards nixpkgs?

Right now, the Marsnix script assumes Nixpkgs is what you want to archive. But the logic of what it does is very simple and it can be modified to work just on a drvPath. https://github.com/nix-how/marsnix/blob/master/pkgs/marsnix/default.nix
Sign in to participate in the conversation
Doma Social

Mastodon server of https://doma.dev.