Soft Fork Maintenance

I have created a POC of this structure in the Github org. Relevant repos:

As a demonstration - you can run nix build github:auxolotl/top-level#javascript.test. The POC consists of 3 repos in the arrangement in @VlinkZ’s diagram.

  • top-level consumes both packages and javascript as inputs, and javascript only consumes top-level.
  • javascript’s output contains a function that accepts packages as input, and exports the hello derivation from top-level.core (ie. the packages flake).
  • top-level’s output contains both the Nixpkgs set from packages, as well as the function from javascript, with the packages flake input passed to it to construct javascript’s package set.

The flakes are pretty barebones, and don’t follow the proper output schema - I just wanted to use this as a quick and dirty POC for now. Obviously, we’d be constructing our flakes a lot nicer than this :stuck_out_tongue: In any case, feel free to take a look and let me know your thoughts in the structure!

4 Likes