Gabriele Modena

> Yes, https://github.com/gmodena/nix-flatpak/issues/82 seems like a much easier solution to this problem and would love to see it be implemented instead! I'm closing this issue since I think that #82...

> Hm, maybe also achieved by just using `org.package.Name/aarch64` in the name. Declaring architecture in the `ref` should do the trick. This is what happens when I install an aarch64...

Hey @orowith2os, This could be interesting to support in the future, but there's a few things I'd like `nix-flatpak` to support before increasing scope (notably: #135 and #82#82 Do you...

thanks for the pointer!

hey @griffi-gh , could you give an example of how managing GPG keys would work? Would you want to wrap `flatpak-builder` or just be able to provide alternative paths to...

Hey @m3thm4th , Thanks for reaching out. The working configuration is described under [Packages](https://github.com/gmodena/nix-flatpak?tab=readme-ov-file#packages). For Flatseal, it would look like this: ``` services.flatpak.packages = [ "com.github.tchx84.Flatseal" ]; ``` > I'm...

The snippet is a flake (https://zero-to-nix.com/concepts/flakes/). You'll need to enable flakes to import the module as documented. refers to the hostname where you'll run the NixOS (or Home Manager) activation....

Hey @baduhai . This should not be too hard to implement, and can def benefit more people. I'll have a look at it after #136.

> This should not be too hard to implement I spoke too quickly. Installing from a file is straightforward, but handling state is not as simple. tl;dr: this work is...

I do have some work in flight on this, that I hope to make available soon-ish. Right now I'm still daily driving it, to iron out some bugs. Working with...