The below imply the rest of the dependencies also, obviously.

- LFS builds
  (better definitions for results in `core` libs)
  (Remove 'result' as a macro input. The `mosaic` definition will just check if the sha256-tesseraName exists or not, since each tessera will be built with its dependencies in the same isolated folder.)
- redefine macro for isolated builds
  (this means that each macro call should be able to pass its own prefix=/... etc, based on sha derivations of the binaries of the tessera (?))
  (Another way to approach this is to make a single tessera include all the definitions of the dependencies so everything is built independently.)
  (Does it beat the idea of a declerative reproducable distro if I symlink between different builds inside the store?)
- make macro accept local paths (for custom changes/patches/development)
- figure out how to handle the kernel
- add `dependants` to macro definition (if a tessera is updated, all its dependants need to be rebuilt) (?)
  (this might not be needed as I can make it work just by walking backwards. an update could trigger a soft rebuild of all packages "twice". Might be wasteful though.)
- xfce4 (?)
- atuin (?) (I will have to package rust...........)