nix-flatpak icon indicating copy to clipboard operation
nix-flatpak copied to clipboard

A script to generate a starting point

Open lucasew opened this issue 2 months ago • 1 comments

This is really cool but in my case, for example, I already have many packages and overrides that I basically lost track of what I did.

For a new user it would be really useful if there was a script to generate a Nix module based on what I already have so then I can start my setup or just retrofeed impure state back to the pure setup.

I may do that, but I opened this at least to gather feedback on how would be the best approach for that.

lucasew avatar Oct 18 '25 12:10 lucasew

Hey @lucasew,

For packages, the easiest approach that comes to mind would be to run flatpak list --app and paste the output into services.flatpak.packages. This assumes you don’t need to handle state or more complex configurations (e.g., version pinning).

For overrides, I’d like to extend nix-flatpak to support out-of-tree or pre-existing configs. That would save you from having to rewrite everything into a Nix config file (PR #162 ).

gmodena avatar Nov 01 '25 07:11 gmodena