| 9 Aug 2023 |
 JoelMcCracken | if you're willing to like advise me somehow (or someone else is) as I work on this i think it would surely help speed it along quite a bit | 19:32:02 |
 mei 🌒& | ah! opposite here. i've tried to figure that issue out a few times but haven't had any luck figuring out where to intercept straight | 19:32:07 |
| mei 🌒& | and I am very willing. NDE being out of date has been an itchy part of my config for a long time | 19:33:01 |
| JoelMcCracken | sounds good, ill start poking at it | 19:34:05 |
| mei 🌒& | lmk when you figure out what's needed of the nix bit. you know the general requirements though right? | 19:34:36 |
| JoelMcCracken | let me jut write out what i'm thinking | 19:35:13 |
| JoelMcCracken | emacs is run w a shim, similar to what currently occurs via nix-straight, which grabs more of the
data besides just the package name (ideally, all of the data)
some lisp is called which looks up the metadata to see how straight.el would
resolve the package (the repo, the commit, etc). this data is serialized (json?)
at subsequent step, nix reads this serialized data, and then constructs an
overlay with the correct packages.
the installation then procedes as it currently does, using this new overlay to
just install the requrired packages.
| 19:39:42 |
| JoelMcCracken | i noticed that these are done as separate... derivations? steps? not sure of the right term here.. in nix-straight; i'm not sure why it needs to be this way | 19:44:10 |
| mei 🌒& | JoelMcCracken: right so, the emacs shim runs in one go, currently collecting just the package names, and it doesn't have a network connection at this point because it's in a Nix build. the package meta is put into a json file, which is the output of this derivation. next up the nix evaluator parses this JSON, and prepares the next derivation using that, reading another derivation's result is called IFD | 19:49:25 |
