Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 12/15] harfbuzz: upgrade 1.7.5 -> 1.8.4
Date: Tue, 17 Jul 2018 17:39:07 +0100	[thread overview]
Message-ID: <20180717163910.3196-12-ross.burton@intel.com> (raw)
In-Reply-To: <20180717163910.3196-1-ross.burton@intel.com>

Signed-off-by: Ross Burton <ross.burton@intel.com>
---
 .../harfbuzz/{harfbuzz_1.7.5.bb => harfbuzz_1.8.4.bb}              | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
 rename meta/recipes-graphics/harfbuzz/{harfbuzz_1.7.5.bb => harfbuzz_1.8.4.bb} (86%)

diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_1.7.5.bb b/meta/recipes-graphics/harfbuzz/harfbuzz_1.8.4.bb
similarity index 86%
rename from meta/recipes-graphics/harfbuzz/harfbuzz_1.7.5.bb
rename to meta/recipes-graphics/harfbuzz/harfbuzz_1.8.4.bb
index 0a9b029461f..4d5964d6bb7 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_1.7.5.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_1.8.4.bb
@@ -11,9 +11,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=e021dd6dda6ff1e6b1044002fc662b9b \
 DEPENDS = "glib-2.0 cairo fontconfig freetype"
 
 SRC_URI = "http://www.freedesktop.org/software/harfbuzz/release/${BP}.tar.bz2"
-
-SRC_URI[md5sum] = "1466ab51fc5aaa6af4065936939cec62"
-SRC_URI[sha256sum] = "84574e1b1f65ca694cb8fb6905309665c0368af18a312357f8ff886ee2f29563"
+SRC_URI[md5sum] = "f176eeda0a4e51a056d3ea6b9e65c27f"
+SRC_URI[sha256sum] = "3c592f86fa0da69e2e0e98cae9f5d5b61def3bb7948aa00ca45748f27fa545fd"
 
 inherit autotools pkgconfig lib_package gtk-doc
 
@@ -30,6 +29,8 @@ EXTRA_OECONF = " \
 
 PACKAGES =+ "${PN}-icu ${PN}-icu-dev"
 
+LEAD_SONAME = "libharfbuzz.so"
+
 FILES_${PN}-icu = "${libdir}/libharfbuzz-icu.so.*"
 FILES_${PN}-icu-dev = "${libdir}/libharfbuzz-icu.la \
                        ${libdir}/libharfbuzz-icu.so \
-- 
2.11.0



  parent reply	other threads:[~2018-07-17 16:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 16:38 [PATCH 01/15] bc: upgrade to 1.07.1 Ross Burton
2018-07-17 16:38 ` [PATCH 02/15] tcf-agent: upgrade to 1.7.0 Ross Burton
2018-07-17 16:38 ` [PATCH 03/15] libyaml: upgrade to 0.2.1 Ross Burton
2018-07-17 16:38 ` [PATCH 04/15] btrfs-tools: upgrade 4.16.1 -> 4.17 Ross Burton
2018-07-17 16:39 ` [PATCH 05/15] gnupg: upgrade 2.2.8 -> 2.2.9 Ross Burton
2018-07-17 16:39 ` [PATCH 06/15] libgpg-error: upgrade 1.31 -> 1.32 Ross Burton
2018-07-17 16:39 ` [PATCH 07/15] sysstat: upgrade 11.7.3 -> 11.7.4 Ross Burton
2018-07-17 16:39 ` [PATCH 08/15] xz: upgrade 5.2.3 -> 5.2.4 Ross Burton
2018-07-17 16:39 ` [PATCH 09/15] strace: upgrade 4.22 -> 4.23 Ross Burton
2018-07-17 16:39 ` [PATCH 10/15] pciutils: upgrade 3.5.6 -> 3.6.1 Ross Burton
2018-07-17 16:39 ` [PATCH 11/15] libinput: upgrade 1.11.0 -> 1.11.2 Ross Burton
2018-07-17 16:39 ` Ross Burton [this message]
2018-07-17 18:23   ` [PATCH 12/15] harfbuzz: upgrade 1.7.5 -> 1.8.4 Khem Raj
2018-07-17 19:21     ` Burton, Ross
2018-07-17 16:39 ` [PATCH 13/15] shared-mime-info: upgrade 1.9 -> 1.10 Ross Burton
2018-07-17 16:39 ` [PATCH 14/15] xf86-input-libinput: upgrade 0.27.1 -> 0.28.0 Ross Burton
2018-07-17 16:39 ` [PATCH 15/15] ca-certificates: upgrade 20170717 -> 20180409 Ross Burton
2018-07-17 17:18   ` Alexander Kanavin

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=20180717163910.3196-12-ross.burton@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@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