Help building a flatpak for qutebrowser

[Alexander Larsson]

On Thu, 2017-06-22 at 01:53 +0100, Ankur Sinha wrote:
> On Wed, 2017-06-21 at 15:54 +0200, Aleix Pol wrote:
> > Yes, I'd recommend using manifests and flatpak-builder.
> > 
> > You can use the platform we are producing that includes Qt already.
> > Maybe you can get inspired with these:
> > https://cgit.kde.org/flatpak-kde-applications.git/tree/
> 
> I started with these. I'm not sure if I understand the flatpak build
> process completely, though. For instance, Qutebrowser is Python based
> and requires PyYAML and so on. So, does one need to specify *all* the
> build requires as modules, and will all the build requires have to be
> built from source too? This effectively results in one specifying the
> complete dependency tree, doesn't it?

Not complete. You can stop whenever a module you need is built into the
runtime you depend on. You can run:

 flatpak run org.kde.Platform//master
 $ less /usr/manifest*

To see what is in the platform. This is what you can rely on at
runtime. Additionally, you can do the same for org.kde.Sdk, which is
what you can rely on at build-time.

Also, much of the things you're depending on are really build-time
dependencies (like pytest, i assume). I would recommend adding a 

"cleanup": ["*"]

to those modules, so they will not ship in the final app.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
       alexl at redhat.com            alexander.larsson at gmail.com 
He's an uncontrollable ninja boxer with a mysterious suitcase handcuffed 
to his arm. She's a transdimensional French-Canadian mermaid with the 
power to see death. They fight crime!