You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you think if flake-compat was changed to provide the same output as builtins.getFlake? That way, most of the logic can be substituted if the builtin exists.
Then the other issue is to select the right shell and packages from the current system, which I think is a separate concern. For this I would propose to extend the flake schema to include currentSystem = { packages = []; devShell = <drv>; <...> }.
With both of these combined, flake-compat is the same as builtins.getFlake, and the flake schema would look something like this:
It's quite close to being a poly-fill for builtins.getFlake, but not quite. It would need to output result without the defaultNix and shellNix attributes. And the input parameters aren't exactly the same as builtins.getFlake either.
It would actually also be really nice if it were possible to add polyfills for builtins.getFlake and builtins.fetchTree (inasmuch as that is possible).
What do you think if flake-compat was changed to provide the same output as
builtins.getFlake
? That way, most of the logic can be substituted if the builtin exists.Then the other issue is to select the right shell and packages from the current system, which I think is a separate concern. For this I would propose to extend the flake schema to include
currentSystem = { packages = []; devShell = <drv>; <...> }
.With both of these combined,
flake-compat
is the same asbuiltins.getFlake
, and the flake schema would look something like this:The text was updated successfully, but these errors were encountered: