Re: GNOME xdg-app runtime doesn't follow the jhbuild modulesets

[Alexander Larsson <alexl redhat com>]

On mån, 2016-05-09 at 21:08 +0200, Sébastien Wilmet wrote:
> On Mon, May 09, 2016 at 02:41:37PM +0200, Bastien Nocera wrote:
> > GtkSourceView, which was in the example, is only used by 4 apps,
> > libpeas is used by 7 of the 24 applications in gnome-apps-nightly.
> > In
> > comparison, gnome-desktop is used by 9 applications.
> VTE is included in the runtime but is used by only 2 apps in
> gnome-apps-nightly (gedit and gnome-builder). So 3 with gnome-
> terminal.

Its not super clear that VTE should be in the runtime. I added it due
to vague concerns about security. 

> BTW VTE is in the gnome-suites-core-deps moduleset, and not in
> meta-gnome-extended-devel-platform. In contrast libpeas is in
> meta-gnome-extended-devel-platform but not in the runtime.
>
> Where is the logic?

The logic is completely unrelated to how the jhbuild module-set is
structured. For instance ModemManager is in gnome-suites-core-deps
because gnome-control-center is in gnome-suites-core and it depends on
it. That does not make it right to put ModemManager into the runtime.

Basically, jhbuild is something completely different than a runtime.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
       alexl redhat com            alexander larsson gmail com 
He's a suicidal Catholic assassin looking for 'the Big One.' She's a 
beautiful paranoid single mother with only herself to blame. They fight 
crime!