From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [PATCH] pango: use qemu to generate pango.modules during rootfs construction
Date: Wed, 07 Sep 2011 18:12:11 -0700 [thread overview]
Message-ID: <4E68166B.2050902@linux.intel.com> (raw)
In-Reply-To: <1314804932.19905.169.camel@phil-desktop>
On 08/31/2011 08:35 AM, Phil Blundell wrote:
> This allows pango to be installed in an image with read-only-rootfs.
>
> Signed-off-by: Phil Blundell<philb@gnu.org>
> ---
> meta/recipes-graphics/pango/pango.inc | 11 +++++++----
> meta/recipes-graphics/pango/pango_1.28.4.bb | 2 +-
> 2 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-graphics/pango/pango.inc b/meta/recipes-graphics/pango/pango.inc
> index a8e99e2..ff3f5dd 100644
> --- a/meta/recipes-graphics/pango/pango.inc
> +++ b/meta/recipes-graphics/pango/pango.inc
> @@ -10,13 +10,13 @@ SECTION = "libs"
> LICENSE = "LGPL"
>
> X11DEPENDS = "virtual/libx11 libxft"
> -DEPENDS = "glib-2.0 fontconfig freetype zlib virtual/libiconv gtk-doc-native cairo ${@base_contains('DISTRO_FEATURES', 'x11', '${X11DEPENDS}', '', d)}"
> +DEPENDS = "glib-2.0 fontconfig freetype zlib virtual/libiconv gtk-doc-native cairo qemu-native ${@base_contains('DISTRO_FEATURES', 'x11', '${X11DEPENDS}', '', d)}"
>
> PACKAGES_DYNAMIC = "pango-module-*"
>
> RRECOMMENDS_${PN} = "${@base_contains('DISTRO_FEATURES', 'x11', 'pango-module-basic-x', '', d)} pango-module-basic-fc"
>
> -inherit gnome
> +inherit gnome qemu
>
> EXTRA_AUTORECONF = ""
>
> @@ -33,9 +33,12 @@ LIBV = "1.6.0"
>
> postinst_prologue() {
> if [ "x$D" != "x" ]; then
> - exit 1
> + if [ ! -f "$D${sysconfdir}/pango/pango.modules" ]; then
> + mkdir -p $D${sysconfdir}/pango
> + PSEUDO_RELOADED=YES ${@qemu_target_binary(d)} -L $D $D${bindir}/pango-querymodules> "$D${sysconfdir}/pango/pango.modules"
> + fi
> + exit 0
> fi
> -
> }
>
> python populate_packages_prepend () {
> diff --git a/meta/recipes-graphics/pango/pango_1.28.4.bb b/meta/recipes-graphics/pango/pango_1.28.4.bb
> index 68ab700..33eac21 100644
> --- a/meta/recipes-graphics/pango/pango_1.28.4.bb
> +++ b/meta/recipes-graphics/pango/pango_1.28.4.bb
> @@ -2,7 +2,7 @@ require pango.inc
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7"
>
> -PR = "r1"
> +PR = "r4"
>
> SRC_URI += "file://no-tests.patch"
>
Merged but we found a problem with qemux86-64, a bug was filed and you
should have received an email
Thanks
Sau!
next prev parent reply other threads:[~2011-09-08 1:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 15:35 [PATCH] pango: use qemu to generate pango.modules during rootfs construction Phil Blundell
2011-09-08 1:12 ` Saul Wold [this message]
2011-09-09 21:19 ` Saul Wold
2011-09-10 8:24 ` Richard Purdie
2011-09-10 9:28 ` Phil Blundell
2011-09-10 9:54 ` Richard Purdie
2011-09-10 11:53 ` Phil Blundell
2011-09-13 17:08 ` Richard Purdie
2011-09-13 17:14 ` Otavio Salvador
2011-09-13 17:25 ` Phil Blundell
2011-09-13 18:33 ` Otavio Salvador
2011-09-13 18:46 ` Saul Wold
2011-09-14 9:10 ` Phil Blundell
2011-09-11 21:33 ` Phil Blundell
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=4E68166B.2050902@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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