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). For example, the following configuration tells Flatpak that the devel branch of the app org.test.Foo from remotes which serve the collection org.test.Collection, and the app org.test.Bar from any remote should be installed:

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).

  • frongt@lemmy.zip
    3·
    2 days ago

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

    • data1701d (He/Him)@startrek.websiteEnglish
      2·
      2 days 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.