From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][meta-efl][meta-gpe][PATCH 0/5] fixes after glib-2.0 upgrade
Date: Mon, 7 May 2012 21:05:42 +0200 [thread overview]
Message-ID: <cover.1336417488.git.Martin.Jansa@gmail.com> (raw)
The following changes since commit f769b97271cf4158ec700d32a56d18a756a1ddcb:
xfsprogs: misc fixes for recipe (2012-05-05 09:00:21 +0200)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib jansa/pull2
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=jansa/pull2
Martin Jansa (5):
libsoup-2.4, gobject-introspection: upgraded in oe-core
libgee: upgrade to 0.6.4
glibmm: fix build with glib-2.32
loudmouth: fix build with glib-2.32
gpe-scap: migrate to use libsoup-2.4 instead of libsoup-2.2 API
.../recipes-support/libsoup/libsoup-2.4_2.37.2.bb | 25 ------------
.../use-usr-bin-env-for-python.patch | 20 ---------
.../gobject-introspection_0.9.10.bb | 32 ---------------
.../gobject-introspection_git.bb | 34 ----------------
.../gpe-scap/gpe-scap/use.libsoup-2.4.patch | 42 ++++++++++++++++++++
meta-gpe/recipes-graphics/gpe-scap/gpe-scap_1.4.bb | 8 ++-
.../loudmouth/loudmouth-1.4.3/glib-2.32.patch | 10 +++++
.../loudmouth/loudmouth_1.4.3.bb | 5 ++-
.../recipes-core/glib-2.0/glibmm/glib-2.32.patch | 10 +++++
meta-oe/recipes-core/glib-2.0/glibmm_2.28.2.bb | 7 +--
.../libgee/{libgee_0.6.0.bb => libgee_0.6.4.bb} | 11 ++---
11 files changed, 79 insertions(+), 125 deletions(-)
delete mode 100644 meta-efl/recipes-support/libsoup/libsoup-2.4_2.37.2.bb
delete mode 100644 meta-gnome/recipes-gnome/gobject-introspection/gobject-introspection/use-usr-bin-env-for-python.patch
delete mode 100644 meta-gnome/recipes-gnome/gobject-introspection/gobject-introspection_0.9.10.bb
delete mode 100644 meta-gnome/recipes-gnome/gobject-introspection/gobject-introspection_git.bb
create mode 100644 meta-gpe/recipes-graphics/gpe-scap/gpe-scap/use.libsoup-2.4.patch
create mode 100644 meta-oe/recipes-connectivity/loudmouth/loudmouth-1.4.3/glib-2.32.patch
create mode 100644 meta-oe/recipes-core/glib-2.0/glibmm/glib-2.32.patch
rename meta-oe/recipes-devtools/libgee/{libgee_0.6.0.bb => libgee_0.6.4.bb} (46%)
--
1.7.8.6
next reply other threads:[~2012-05-07 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 19:05 Martin Jansa [this message]
2012-05-07 19:05 ` [meta-oe][meta-efl][meta-gpe][PATCH 1/5] libsoup-2.4, gobject-introspection: upgraded in oe-core Martin Jansa
2012-05-07 19:05 ` [meta-oe][meta-efl][meta-gpe][PATCH 2/5] libgee: upgrade to 0.6.4 Martin Jansa
2012-05-07 19:05 ` [meta-oe][meta-efl][meta-gpe][PATCH 3/5] glibmm: fix build with glib-2.32 Martin Jansa
2012-05-07 19:05 ` [meta-oe][meta-efl][meta-gpe][PATCH 4/5] loudmouth: " Martin Jansa
2012-05-07 19:05 ` [meta-oe][meta-efl][meta-gpe][PATCH 5/5] gpe-scap: migrate to use libsoup-2.4 instead of libsoup-2.2 API Martin Jansa
[not found] ` <cover.1336418115.git.Martin.Jansa@gmail.com>
2012-05-07 19:17 ` [meta-oe][meta-efl][meta-gpe][PATCH 6/7] kernel.bbclass: move kernel-vmlinux up in PACKAGES Martin Jansa
2012-05-07 19:17 ` [meta-oe][meta-efl][meta-gpe][PATCH 7/7] kernel.bbclass: Use kmod-native instead of module-init-tools-cross Martin Jansa
2012-05-07 19:41 ` Martin Jansa
2012-05-07 20:17 ` 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=cover.1336417488.git.Martin.Jansa@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.