Geary 0.11.1 flatpak (version 2)

[Alexander Larsson]

On Fri, 2016-07-01 at 12:19 +1000, Michael Gratton wrote:
> On Fri, Jul 1, 2016 at 1:33 AM, Alexander Larsson <alexl at redhat.com> 
> wrote:
> > On Wed, 2016-06-29 at 11:53 +0100, Emmanuele Bassi wrote:
> > >  Hi;
> > > 
> > >  On 29 June 2016 at 11:10, Mattias Eriksson <snaggen at gmail.com> 
> > > wrote:
> > >  > I was told that the geary flatpak i had issues with the About
> > >  > dialog image,
> > >  > missing locales and help not working. I have fixed the image
> > > and
> > >  > locale
> > >  > problems, but I'm not sure how to fix the problem with the
> > > Help 
> > > not
> > >  > working?
> > > 
> > >  In order to launch the help browser you need a portal — you
> > > cannot
> > >  see
> > >  all the installed applications from within the sandbox, so
> > > there's
> > >  nothing with which you can open the help URI. The "launch 
> > > application
> > >  appropriate for this URI" portal is in progress; as soon as it's
> > >  available, help links should go back to working.
> > 
> > Actually help is pretty complicated, for several reasons.
> > 
> 
> [snip]
> 
> > 
> > Maybe we should just bundle the help browser with the gnome
> > runtime?
> > That will conflict with the cross-app help references though...
> 
> What if apps placed their help files in a well-known location under 
> /export? If the external links use app names or can be somehow
> indexed 
> into them, then if the runtime bundles a help browser that
> understands 
> this it should Just Work™, right?

Exporting a massive set of data to the host which depends on some
vaguely defined version of some webbrowser seems both risky and likely
to lead to problems down the line. There is still no guarantee that the
host has support for reading the version of your docs, or at all, and
also this gives a vector to export any kind of files to the host which
may risk code execution outside the sandbox.

Honestly, I think its better if each desktop bundles their help browser
in their runtime. 

> Relatedly, I'd like to get Geary into the Flatpak gnome-apps repo. 
> What's the correct process? Can I just commit the JSON file to the 
> branches in git.gnome.org/gnome-apps-nightly?

Yeah, just commit it. Unstable git builds to "master" branch and 3.20
versions to the "3-20" branch. Unfortunately the nightly unstable
builds are a bit busted atm, because of a build failure in gjs:

  https://bugzilla.gnome.org/show_bug.cgi?id=768088

So, we don't have a working build of latest master runtime, and thus no
latest master apps.

Also, the newly built stable apps (as well as runtimes) are not
automatically migrated to the official repo. The x86 builds are done
here: http://sdkbuilder1.gnome.org/repo/ signed with the nightly keys.
Migrating and re-signing with the official stable key is a manual
process.