Flathub JSON recipes

[Alexander Larsson]

On Mon, 2017-08-14 at 07:35 -0400, intrigeri wrote:
> Hi,
> 
> just my 2cts on one specific technical detail (I have no strong
> opinion on the broader topic):
> 
> Alexander Larsson:
> > However, the stable build is much more
> > problematic. First of all, where does it go? The natural place
> > would be
> > on the stable branch, but that is often (at least for gnome) based
> > on
> > the actual version nr (e.g. gnome-3-22), so the branch to use to
> > find
> > the manifest to build kept changing as things were released.
> 
> One solution for projects whose stable branch keeps changing name
> would be to maintain a signed Git tag (say, "flatpak-stable")
> pointing
> to the release one wishes to see tracked on Flathub. Granted, it's
> one
> more step from the maintainer's PoV, can be forgotten, etc. Signed
> Git
> tags can be overwritten and propagate nicely across repos and
> working copies.

Another thing that we don't get for non-github repos is change
notification. I.e. how do we know there is a new json to build? We
don't get notifications for repos that are not on github, and if the
repo mixes regular code and changes to the json manifest we can't
reliably tell when we need to rebuild.

So, another alternative is to allow the github repo to contain a file
that points to a particular version of a json manifest in another repo,
and change that whenever you want to rebuild it. Otoh, at this point it
seems more work than just making a copy of it into the flathub repo.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
       alexl at redhat.com            alexander.larsson at gmail.com 
He's a witless overambitious werewolf She's a ditzy belly-dancing lawyer 
from out of town. They fight crime!