Flathub, on the other hand, is more open when it comes to how developers bundle applications.

First and foremost, Fedora Flatpaks literally converts existing RPMs to Flatpak-compatible files where developers can then easily bundle as Flatpak and redistribute them.

Packagesįedora Flatpaks and Flathub create Flatpak applications differently. Filing issues for applications provided by Flathub is the same as filing issues on any project on GitHub. Hence, all tools are available on GitHub.

Of course, it’s always advisable to keep everything up-to-date.įlathub’s motivation is to simply make applications and tools as accessible as possible regardless of the distribution in use. So, in theory, it would be possible to get the latest and greatest applications from the Fedora Project without needing to upgrade to the latest version of Fedora Linux. The goal is to make applications accessible in their respective field, maximize convenience and minimize maintenance.įedora Flatpaks’s motivation is to push RPMs that come directly from the Fedora Project and make them accessible throughout Fedora Linux regardless of the versions, spin, etc. Goals and motivationįedora Flatpaks and Flathub share the same goals but differ in motivation. The things that differ between the remotes include but are not limited to their policies, their ways of distribution, and their implementation. Flathub is the de-facto standard Flatpak remote, whereas Fedora Flatpaks is the Fedora Project’s Flatpak remote.

This article compares and contrasts between the Fedora Flatpaks remote and the Flathub remote. In the previous article in this series, we looked at how to get started with Fedora Flatpaks and how to use it.

Flathub spotify