2
Flatpak Pre-Installation Approaches (blog.sebastianwick.net)
submitted 11 months ago by to c/flatpak@programming.dev
comment fedilink hide all child comments
 

Together with my then-colleague Kalev Lember, I recently added support for pre-installing Flatpak applications. It sounds fancy, but it is conceptually very simple: Flatpak reads configuration files from several directories to determine which applications should be pre-installed. It then installs any missing applications and removes any that are no longer supposed to be pre-installed (with some small caveats).

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
3 comments in c/linux@programming.dev view that post
[–] 3 points 11 months ago (1 child)

What's the advantage of this over a whole-system provisioning system like ansible?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 2 points 11 months ago

    From what I can tell, you wouldn't use it instead of Ansible or another automation system, but rather just support for a config file you can plot in to make setting up automation with any automation system easier by allowing you to put it into a file rather than a gigantic Flatpak install command.

  • permalink
  • fedilink
  • source
  • parent
    • [–] -1 points 11 months ago

    Flatpak is unironically dead. It provides next to no security benefits. Single store with no verification of updates. Worse compatibility with other system apps. Its only positive is that it gives developers a single linux platform to target but it even does a bad job at that since the developer experience is subpar compared to snap and app image.

    Apart from having a good name its kinda bad at everything.

  • permalink
  • fedilink
  • source
    •