Концепции Flatpak

Идентификатор приложения

Каждому приложению необходим уникальный идентификатор приложения, основанный на обратном доменном имени. Например, org.gnome.Maps. Все ресурсы, экспортируемые приложением, должны иметь префикс этого идентификатора. Сюда входят desktop file, файл данных приложения и любые значки, на которые ссылается файл desktop.

Смотрите Picking an application ID.

Данные приложения

Файл данных приложения для Flatpak используется для отображения информации о приложении перед установкой. См. Fedora Packaging Guidelines for AppData Files.

Среды выполнения и связанные библиотеки

Когда Flatpak выполняется, файлы, которые видит приложение, поступают из двух мест:

  • The Flatpak runtime, mounted at /usr. This contains libraries and data files shared by all Fedora Flatpaks. There are runtimes for each Fedora release.

  • The Flatpak application, mounted at /app. This contains the application code itself, but also contains any libraries that are bundled with the application. The application and libraries must be rebuilt with this prefix - this is done by rebuilding them for flatpaks.

RPM builds

Packaging flatpaks in Fedora makes use of RPM builds. The application and bundled libraries are rebuilt in Fedora’s build system (Koji) with a special build target - this gives a couple of advantages:

  • The same RPM spec file used to create the regular RPM build is also used to create the Flatpak RPM build.

  • The Flatpak RPM build target has a different buildroot configuration with macros that result in RPMs being built with a prefix of /app.

Note that Flatpak RPM builds will not work outside the Flatpak context, since they are rebuilt with a prefix of /app with the same name as system libraries - you cannot use dnf install to install them.

Образы OCI

For Fedora, Flatpak runtimes and applications are built as OCI Images and distributed via https://registry.fedoraproject.org. This allows Flatpaks to be handled in a very similar way to server side containers. (Flatpaks are also commonly distributed via ostree.)

Want to help? Learn how to contribute to Fedora Docs ›