ok, but the part i have right now isn't even invok...
# development
a
ok, but the part i have right now isn't even invoking cargo, it's creating an environment so that cargo can be invoked in a subsequent process execution without having to hit the internet for 3rdparty deps. being able to extract the resolve process out of the compile process via cargo-fetcher lets us do that, which is why i wanted to focus on it as a first milestone
w
i’m thinking of the portion that stores things in an lmdb via an intrinsic
a
yes, i just responded to the comment
i totally agree now
took me a second to get my head around the append-only caching stuff but it jives really strongly with what i think i want to have from brfs (where reads are virtualized from the fs store, and writes are virtualized to this mutable cache in the sky)