Flatpak as part of the development process

[Christian Hergert]

On 04/04/2017 04:17 PM, Aleix Pol wrote:
> So you are inferring that the only *.*.*.json file there's available
> in the root of the project is a flatpak build manifest?
> 
> In fact, it would be interesting to have a mimetype for
> flatpak-build-manifests, at the moment it's just json, which doesn't
> help much.

Builder scans the project directory for files that looks like JSON
manifests and then checks them by peeking in, decoding, and verifying.

We have a concept called "Configuration Providers", and the flatpak
plugin implements this. The user can switch between configurations (and
flatpak manifests map 1:1 with a Configuration).

We have various projects that are transitioning build systems (from
autotools to meson), so we have another layer that can infer the proper
incremental build system to use from the manifest as well. Although I'm
not exactly pleased with our design there. But it works™.

-- Christian