From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt5base: add 3rdparty/harfbuzz-ng license file hash
Date: Mon, 6 Nov 2017 22:24:39 +0100 [thread overview]
Message-ID: <20171106222439.2467dcf1@gmx.net> (raw)
In-Reply-To: <0af4065c-c126-fab5-82cc-b95d07114267@mind.be>
Hello Arnout,
On Sun, 5 Nov 2017 15:59:14 +0100, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 23-10-17 19:44, Peter Seiderer wrote:
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> Applied to master, thanks.
>
> You're building qt5 on sparc or m68k then? Those are the only platforms where
> the internal harfbuzz (and thus this license file) will be used...
No, I am a ordinary ARM user (mostly)...., but in between the first version
of the qt5base/harfbuzz patch and the commit lately the license file hash
check was introduced ;-)
Regards,
Peter
>
> Regards,
> Arnout
>
> > ---
> > package/qt5/qt5base/qt5base.hash | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/package/qt5/qt5base/qt5base.hash b/package/qt5/qt5base/qt5base.hash
> > index 2a073d4753..4883484d5b 100644
> > --- a/package/qt5/qt5base/qt5base.hash
> > +++ b/package/qt5/qt5base/qt5base.hash
> > @@ -11,3 +11,4 @@ sha256 0dbe024961f6ab5c52689cbd036c977975d0d0f6a67ff97762d96cb819dd5652 LICENSE.
> > sha256 68afaf3392f8c04218fbf29db43cc0b18bf651c1db086556aa584046de9f3e35 LICENSE.LGPLv3
> > sha256 ed8742a95cb9db653a09b050e27ccff5e67ba69c14aa2c3137f2a4e1892f6c0d LICENSE.FDL
> > sha256 8fdefa0b45d9f791f687da6c2c4c83c1b701aaee2c08008f55d522af214b88f0 header.BSD
> > +sha256 2a886915de4f296cdae5ed67064f86dba01d0c55286d86e8487f2a5caaf40216 src/3rdparty/harfbuzz-ng/COPYING
> >
>
prev parent reply other threads:[~2017-11-06 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 17:44 [Buildroot] [PATCH v1] qt5base: add 3rdparty/harfbuzz-ng license file hash Peter Seiderer
2017-11-05 14:59 ` Arnout Vandecappelle
2017-11-06 21:24 ` 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=20171106222439.2467dcf1@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