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

[Sébastien Wilmet <swilmet gnome org>]

On Mon, May 09, 2016 at 08:10:59AM -0400, Matthias Clasen wrote:
> On Sun, May 8, 2016 at 8:25 AM, Sébastien Wilmet <swilmet gnome org> wrote:
> > Less on-topic, but why some GNOME-hosted libraries like libpeas are in
> > meta-gnome-extended-devel-platform and some are in
> > gnome-suites-core-deps? I thought that all the GNOME libraries were part
> > of the GNOME development platform. If officially it is not the case, in
> > practice it is, since by definition GNOME core depends on them.
>
> Being hosted on gnome.org is not directly related to being part of the
> GNOME development platform.

Sure, but I meant the dependencies of GNOME core, and hosted on
gnome.org. In other words the modules present in gnome-suites-core-deps
and that are hosted on gnome.org. Those should be part of "the GNOME
development platform", no? if such definition exists.

> > For non-GNOME-hosted libraries, then it makes sense to not include them
> > in the GNOME runtime, of course.
>
> Not really, no. The runtime needs to be dependency-closed. Where
> something is hosted does not really figure into this much. For
> example, GTK+ depends on cairo (freedesktop.org), harfbuzz
> (freedesktop.org), epoxy (github). All of these need to be in the
> runtime for GTK+ to work.

Yes, the runtime needs to work. I meant the non-GNOME-hosted libraries
present in gnome-suites-core-deps and currently missing in the GNOME
runtime.

--
Sébastien