couple problems found during the process

• most of the attributes exported from manifests are not used at all
• libraries (Init Std Lean Lake) are already included package, need to find a way to re-expose them
• if locked nixpkgs version is too outdated, build might fail, user level override may be needed
• bootstrapped manifests all have IFD, eval time is unbearably slow

Does this mean every future Lean version will have a ${version}.nix and ${version}-bin.nix in the manifest?

we can do that or just add a bootstrap-bin or whatever function inside ${version}.nix

ideally -bin variants should only depend on tag and rev

we can do that or just add a bootstrap-bin or whatever function inside ${version}.nix

ideally -bin variants should only depend on tag and rev

What's the point of doing this when you have to build the entire Lean binary anyways

i was thinking of implementing this by overriding pkgs.lean4 so we can reuse the nixpkgs binary cache

apparently it won't work unless we pin multiple versions of nixpkgs in flake inputs