From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] package/harfbuzz: bump to version 2.6.8
Date: Thu, 10 Sep 2020 20:20:46 +0200 [thread overview]
Message-ID: <20200910202046.4c7f1ca4@gmx.net> (raw)
In-Reply-To: <20200910181152.22026-1-ps.report@gmx.net>
....ups, drop this patch series (forgot to git rebase --continue)...., update follows...
Regards,
Peter
On Thu, 10 Sep 2020 20:11:51 +0200, Peter Seiderer <ps.report@gmx.net> wrote:
> From: Francois Perrad <fperrad@gmail.com>
>
> - update home page URL (old one is redirected to github)
> - change download to new location (github)
> - update license hash because of copyright year update:
>
> diff COPING:
> -Copyright ? 2010,2011,2012,2013,2014,2015,2016,2017,2018,2019 Google, Inc.
> -Copyright ? 2019 Facebook, Inc.
> +Copyright ? 2010,2011,2012,2013,2014,2015,2016,2017,2018,2019,2020 Google, Inc.
> +Copyright ? 2018,2019,2020 Ebrahim Byagowi
> +Copyright ? 2019,2020 Facebook, Inc.
>
> note: newer versions (2.7.x) require a migration to meson
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/harfbuzz/Config.in | 2 +-
> package/harfbuzz/harfbuzz.hash | 6 ++----
> package/harfbuzz/harfbuzz.mk | 4 ++--
> 3 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/package/harfbuzz/Config.in b/package/harfbuzz/Config.in
> index e8f407bb8f..27fa102e1f 100644
> --- a/package/harfbuzz/Config.in
> +++ b/package/harfbuzz/Config.in
> @@ -6,7 +6,7 @@ config BR2_PACKAGE_HARFBUZZ
> help
> HarfBuzz is an OpenType text shaping engine
>
> - http://www.freedesktop.org/wiki/Software/HarfBuzz/
> + https://harfbuzz.github.io/
>
> Harfbuzz can make optional use of cairo, freetype,
> glib2 and icu packages if they are selected.
> diff --git a/package/harfbuzz/harfbuzz.hash b/package/harfbuzz/harfbuzz.hash
> index ba54f477aa..660e19efc9 100644
> --- a/package/harfbuzz/harfbuzz.hash
> +++ b/package/harfbuzz/harfbuzz.hash
> @@ -1,5 +1,3 @@
> -# From https://www.freedesktop.org/software/harfbuzz/release/harfbuzz-2.6.4.tar.xz.sha256
> -sha256 9413b8d96132d699687ef914ebb8c50440efc87b3f775d25856d7ec347c03c12 harfbuzz-2.6.4.tar.xz
> -
> # Locally computed
> -sha256 1b32b6e2fea50440c128c5ba482f7691367c46fd0cd573b80fc863bf07964cea COPYING
> +sha256 6648a571a27f186e47094121f0095e1b809e918b3037c630c7f38ffad86e3035 harfbuzz-2.6.8.tar.xz
> +sha256 beb3f017ceb41387667f78237a7cecf84defa0ed257c505894663d6a9f13211b COPYING
> diff --git a/package/harfbuzz/harfbuzz.mk b/package/harfbuzz/harfbuzz.mk
> index 3006b5ab98..c7bb8f9347 100644
> --- a/package/harfbuzz/harfbuzz.mk
> +++ b/package/harfbuzz/harfbuzz.mk
> @@ -4,8 +4,8 @@
> #
> ################################################################################
>
> -HARFBUZZ_VERSION = 2.6.4
> -HARFBUZZ_SITE = https://www.freedesktop.org/software/harfbuzz/release
> +HARFBUZZ_VERSION = 2.6.8
> +HARFBUZZ_SITE = https://github.com/harfbuzz/harfbuzz/releases/download/$(HARFBUZZ_VERSION)
> HARFBUZZ_SOURCE = harfbuzz-$(HARFBUZZ_VERSION).tar.xz
> HARFBUZZ_LICENSE = MIT, ISC (ucdn library)
> HARFBUZZ_LICENSE_FILES = COPYING
prev parent reply other threads:[~2020-09-10 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 18:11 [Buildroot] [PATCH v1 1/2] package/harfbuzz: bump to version 2.6.8 Peter Seiderer
2020-09-10 18:11 ` [Buildroot] [PATCH v1 2/2] package/harfbuzz: bump version to 2.7.2 Peter Seiderer
2020-09-10 18:20 ` Peter Seiderer [this message]
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=20200910202046.4c7f1ca4@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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