From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-gnome 2/2] libnotify: update to 0.7.5 and drop libnotify3
Date: Thu, 18 Apr 2013 13:00:26 +0200 [thread overview]
Message-ID: <20130418110026.GO26007@jama> (raw)
In-Reply-To: <CALbNGRTfQh7iBf=8XceW1mJ2mCttp4ccB77p9o9LtMkS0kMYUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
On Thu, Apr 18, 2013 at 11:53:45AM +0200, Andreas Müller wrote:
> On Thu, Apr 18, 2013 at 10:22 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Thu, Apr 18, 2013 at 08:58:24AM +0200, Andreas Müller wrote:
> >> On Wed, Apr 17, 2013 at 4:01 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> > Hash: SHA1
> >> >
> >> > Op 17-04-13 15:49, Andreas Müller schreef:
> >> >> removing tests drops dependencies on gtk
> >> >>
> >> >> Tested by:
> >> >>
> >> >> * building nautilus3 (the only recipe found depending on libnotify3) *
> >> >> running xfce-based image and checked notififations
> >> >
> >> > The problem with libnotify was (is?) that it removed some API that GNOME 2.x
> >> > depends on and later introduced API that GNOME 3.x depends on, hence the 2
> >> > recipes. Do all the GNOME 2.x bits build against this new libnotify? The
> >> > error was a build break, so it things build, they are likely to work :)
> >> >
> >> > regards,
> >> >
> >> > Koen
> >> >
> >> Martin's world shall let us know
> >
> > My slaves are looking forward to serve..
> >
> > It's in queue, but still jenkins is 40+ hours behind, so I'll let you know later..
> >
> I started and additional test. At least zenity fails for API change
> but seems not a big deal to fix. Will send follow up patches.
I guess that to test this properly I should cleansstate both libnotify
or do build from scratch, because I cannot know which one won
into-the-sysroot race during last build.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-04-18 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 13:49 [meta-gnome 1/2] gnome-desktop3: add gnome-common to DEPENDS Andreas Müller
2013-04-17 13:49 ` [meta-gnome 2/2] libnotify: update to 0.7.5 and drop libnotify3 Andreas Müller
2013-04-17 14:01 ` Koen Kooi
2013-04-18 6:58 ` Andreas Müller
2013-04-18 8:22 ` Martin Jansa
2013-04-18 9:53 ` Andreas Müller
2013-04-18 11:00 ` Martin Jansa [this message]
2013-04-18 11:24 ` Andreas Müller
2013-04-18 12:45 ` Andreas Müller
2013-04-26 17:00 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130418110026.GO26007@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox