| 7 Sep 2023 |
 JoelMcCracken | but yeahwe should be able to share a lot of all of this code | 14:12:20 |
| JoelMcCracken | it would be v nice if elpaca had some design input from us | 14:13:08 |
| JoelMcCracken | so that we could just interface with it instead of having to hack it | 14:13:25 |
 mei 🌒& | my thought was, main Emacs goes "I want this straight recipe (package! blabla :pin "whatever")" and system()s a nix-build --argstr recipe "…", then there's another little Emacs spawned inside the Nix sandbox which is a FOD and has network access, so it goes on fetching that package and then brings the output back through Nix to the main Emacs | 14:14:07 |
| JoelMcCracken | yep | 14:14:25 |
| JoelMcCracken | tho, FOD? | 14:14:42 |
| mei 🌒& | fixed-output derivation, a sorta precondition to getting network access in the nix sandbox | 14:14:56 |
| JoelMcCracken | ic | 14:15:03 |
| mei 🌒& | you know, the hash option you set when you use fetchFromSomething | 14:15:06 |
| JoelMcCracken | k | 14:15:12 |
| mei 🌒& | * you know, the hash attr you set when you use fetchFromSomething | 14:15:14 |
