Packaging flatpaks in Fedora makes use of https://docs.fedoraproject.org/en-US/modularity/[Modularity]. The application and bundled libraries are built in a module - this gives a couple of advantages:

   * The module has a different buildroot configuration with macros that result in RPMs in the module being built with a prefix of `/app`.

  Note that Flatpak modules will not work outside the Flatpak context, since they contain RPMs rebuilt with a prefix of `/app` with the same name as system ibraries - you cannot use `dnf module enable` to install them.

  Applications can only export resources under their application ID, so the desktop file and icon for the application need the appropriate name. The best place to implement this is upstream. The second best place is in the Fedora application package. But if this isn’t possible, you can do this in your container.yaml. See the <<Renames>> section below.

  == Versioning

  A flatpak targets a particular runtime. Your stable version should ideally target the runtime corresponding to the latest released version of Fedora. If the released upstream stable version of the application has dependencies that are not available in a released version of Fedora and that can’t be bundled in your application module (e.g. it requires a newer version of the C compiler) then it’s acceptable to use the next version of the Fedora runtime, but this should be an unusual case. Your application might be based on the flatpak-runtime:f28 module, for example.

        libpeas:

          repository: file:///<path to checkouts>/libpeas

          rationale: Runtime dependency

  ----

  * Use `fedpkg switch-branch` to switch to the rfe from `<application.yaml>` (or change the `ref:` in `<application.yaml`> to be `master`)

  === Quickly debugging prefix=/app builds

  If you hit a problem where a component fails to build with prefix=/app and you need to debug in detail,

  as a shortcut, you can *temporarily*

  try rebuilding the package with `fedpkg local`,

  fix problems,

  then uninstall flatpak-rpm-macros.

      - MIT

    dependencies:

    - buildrequires:

      requires:

    profiles: <2>

      default:

        rpms:

        feedreader: <3>

          buildorder: 10

          rationale: Application package

        gnome-online-accounts: <5>

          rationale: Runtime dependency

        gumbo-parser: <5>

          rationale: Runtime dependency

        libpeas: <5>

          rationale: Runtime dependency

  ...

  ----

  <1> Source and description come from RPM metadata

  https://pagure.io/releng as follows:

  ....

  ....

  (https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.org/thread/ANZRNH75N7MHRO6VEUNT4WOMHO5PNXGW/[devel@lists.fedoraproject.org thread about automating])