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

[Alexander Larsson <alexl redhat com>]

On sön, 2016-05-08 at 14:25 +0200, Sébastien Wilmet wrote:
> On Sun, May 08, 2016 at 01:23:52PM +0200, Bastien Nocera wrote:
> > On Sun, 2016-05-08 at 13:17 +0200, Sébastien Wilmet wrote:
> > > I see that GtkSourceView is not in the GNOME xdg-app runtime. But
> > > GtkSourceView is part of GNOME core, AFAIK, since it's present in
> > > the
> > > gnome-suites-core-deps jhbuild moduleset.
> > >
> > > Why is the moduleset not followed?
> > gnome-suites-core-deps is the dependencies for GNOME core, not
> > GNOME
> > core.
> The GNOME xdg-app runtime includes some modules of
> meta-gnome-extended-devel-platform (part of GNOME core, if I follow
> correctly), but not all. For example WebKitGTK+ is included, but
> libpeas
> is not.

WebKitGtk+ is in the runtime for three reasons:
1) It security sensitive, so we want to share maintainance burden
2) Quite a lot of apps seem to use it, as web stuff is common these 
   days
3) It is a major pain in the ass to build, so we save people a lot
   of pain having to bundle it

libpeas is pretty easy to build, and doesn't get exposed to network
data, so its not particularily security sensitive. Its somewhat
commonly in use, although less than e.g. gtk+, but individual apps may
want to build it in different ways. For instance, if we wanted to ship
it in the runtime with every backend supported we'd have to add lua and
pygobject2 to the runtime also. And if we didn't apps would have to
build their own libpeas anyway.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
       alexl redhat com            alexander larsson gmail com 
He's a sword-wielding vegetarian boxer trapped in a world he never made. 
She's a bloodthirsty bisexual detective prone to fits of savage, 
blood-crazed rage. They fight crime!