Flatpak as part of the development process

[Aleix Pol]

On Fri, Mar 31, 2017 at 8:04 PM, Christian Hergert <christian at hergert.me> wrote:
> On 03/31/2017 11:26 AM, Aleix Pol wrote:
>> To solve this issue, I'd suggest allowing the project directory using
>> a relative path to the json file. This will allow to compile what we
>> already have, without the round-trip.
>>
>> sources: [ { "type": "file", "path": "." } ]
>>
>> That said, this could have problems, such as these relative paths
>> going outside of the project (e.g. "../myawesomelibrary"). This should
>> be an error.
>>
>> Does that make sense to you? Am I missing something?
>
> In Builder, we only use flatpak-builder for dependencies and --run for
> running. For the "top-most" project, we use our normal incremental build
> system abstraction (for which we got the .json file).
>
> So to start building and contributing to a project, all you need to do
> when Builder opens is: Clone -> Paste Project URL -> Clone -> Run and
> everything happens behind the scenes as you'd expect.

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.

Aleix