babel
X multi-version optional dependencies for PubGrub
Which as far as I can tell hasn’t been done before.
PubGrub opam dependency provider
X json representation of opam repositories
using opam2json
X parse json representation to rust
using serde
O minimal example
O proper opam version parsing (a la Debian)
O conflicts
O boolean logic (package formula)
O features (optional dependencies)
O parse repo on the fly in the dependency provider
O create babel-repository and babel-solver
O explore error reporting in these exotic encodings
what is the research advance here?
- tool to solve across ecosystems
- de-duplication between names
- evaluate the tooling
- need to evaluate against a base case, and justify that the problem exists
- could use the PubGrub formalism, though I think ours is slightly different
O read up on answer set programming
https://pubgrub-rs-guide.pages.dev/internals/intro is a good starting point
spoke to anil about bushel (the new static site generator)
had some interesting thoughts on using the at proto with capnroto capabilities to e.g. update dns records
Spatial Name System
Got capnproto compiling for an ESP chip with Josh (we think)
https://github.com/j0shmillar/esp-capnp-test need to test it with a simple RPC
Sent ‘Practical Modelling with Bigraphs’ over to Roy [1]
27 Jan 2025
Previous: 20 Jan 2025
Next: 3 Feb 2025
[1]
B. Archibald, M. Calder, and M. Sevegnani,
“Practical Modelling with
Bigraphs,” May 31, 2024. [Online]. Available: http://arxiv.org/abs/2405.20745.
[Accessed: Jan. 29, 2025]