Gabriele Modena

This does not seem to be an issue with nix-flatpak. @griffi-gh thanks for the pointers.

Hey @thomasfinstad , thanks for reaching out. Agree. `onActivation`, as currently implemented and documented, is a mess. > How I understand it from the description this option, when set to...

> onActivation should not be enabled if set to false in my opinion. And if you use null as a deactivation switch on onCalendar, then the enable/disable option will be...

> > onActivation should not be enabled if set to false in my opinion. And if you use null as a deactivation switch on onCalendar, then the enable/disable option will...

> [@gmodena](https://github.com/gmodena) I have given the branch a quick try and with my current config I don't see much difference. It seems stable, and still does a install / update...

@thomasfinstad no worries! thanks for the heads up & productive conversations.

Modulo bugs, if you disable updates both on activation and on a fixed schedule, your applications will never be updated. > I see that they are installed immediately during nixos...

I am not involved with nixos/nixpkgs development, but I don't see a path to upstream. The approach followed by `nix-flatpak` does indeed break reproducibility guarantees that nix provides. This project...

Hey @mainrs > Would enforcing commit hashes to pin the flatpaks to a specific version still break reproducubility? Pinning packages should help with reproducbility, to the degree of which specific...

Hey @SpiderUnderUrBed , I'm working on adding the capability to install from local flatpaks (as a way to improve testing). I need to look into supporting generic URI, but that...