Re: [gnome-love] jhbuild and libnotify

[Frederic Peters <fpeters 0d be>]

Iago Toral Quiroga wrote:

> I've seen that some modules fail to build for me because they link
> against my system libnotify (which is linked against other system
> libraries like gtk), thus making those modules try to link against the
> system libraries instead the jhbuild ones.
>
> libnotify is not built by default, so to fix this one should run
> manually:
>
> jhbuild buildone libnotify
>
> and then try to rebuild the broken modules.

You can also have something like this in your .jhbuildrc:

  modules = ['meta-gnome-desktop', 'libnotify', 'notification-daemon']


> shouldn't jhbuild build libnotify by default? otherwise modules like
> gnome-applets, evolution, seahorse or gnome-power-manager, which are
> built by default, will not build properly.

libnotify is not part of any official GNOME suite, and is not a blessed
external dependency; therefore no module should depend on it.

gnome-applets jhbuild module doesn't reference libnotify (but it could
list libnotify in <after> or <suggests>).

evolution has libnotify in its <after> element, which means it will put
evolution after libnotify when calculating module build order, if
possible.

gnome-power-manager has libnotify in its <suggests> element, which means
it doesn't matter if libnotify is built or not.

seahorse has a dependency on libnotify in its jhbuild module definition,
but is not part of any official GNOME suite. (and libnotify can be
disabled with --disable-libnotify).


Regards,

        Frederic