Closed edolstra closed 2 years ago
This could be useful for users to nixify an existing project. Since we're already generating a temporary flake.nix, this should be pretty easy to implement.
I think we will want this, but an important early feature of Riff is the network effect of dependencies defining their own inputs, and the Riff dependency tree becoming richer automatically.
Creating a path "out" of Riff today sort of implies that the goal is to stop using it. I could see a future where we have a really nicely defined workflow from Riff -> pure and good Nix use, but I don't want to go down that road today.
I'm going to close this for now and mark the ticket for revisiting in a few weeks.
It also has a
--stdout
option to writeflake.nix
to stdout, which may be useful to see what riff is doing.Unfortunately,
flake.nix
is not pretty-printed, so the output is rather ugly.