From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5: bump latest version to 5.9.1
Date: Fri, 14 Jul 2017 10:35:18 +0200 [thread overview]
Message-ID: <20170714103518.66ca2b7e@windsurf> (raw)
In-Reply-To: <2a450d8b-10a6-2be9-b7a7-a659a47bffb0@mind.be>
Hello,
On Fri, 14 Jul 2017 00:46:50 +0200, Arnout Vandecappelle wrote:
> Or we could look for pkg-$(VERSION).hash and fall back to pkg.hash if that
> doesn't exist. But it does complicate the code somewhat.
On my side, I continue to think that mixing in the same .hash file the
hashes for download artefacts (tarballs, patches, etc.) and hashes for
files that are extracted from the tarball is very confusing.
Shouldn't we have a separate hash files for the license files, and have
this file in the per-version subdirectory ?
There's admittedly a down-side to this: for most packages, we would
have one hash file containing a single hash for the tarball, and
another hash file containing a single hash for the single license file.
Maybe that's a bit too much.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-14 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 18:00 [Buildroot] [PATCH] package/qt5: bump latest version to 5.9.1 Joshua Henderson
2017-07-12 0:45 ` Arnout Vandecappelle
2017-07-12 1:41 ` Brent Sink
2017-07-12 7:23 ` Arnout Vandecappelle
2017-07-12 15:55 ` Joshua Henderson
2017-07-12 23:04 ` Joshua Henderson
2017-07-13 0:51 ` Joshua Henderson
2017-07-13 7:50 ` Thomas Petazzoni
2017-07-13 15:32 ` Yann E. MORIN
2017-07-13 22:46 ` Arnout Vandecappelle
2017-07-14 8:35 ` Thomas Petazzoni [this message]
2017-07-14 13:12 ` Peter Korsgaard
2017-07-14 13:36 ` Thomas Petazzoni
2017-07-14 13:49 ` Peter Korsgaard
2017-07-16 17:25 ` Yann E. MORIN
2017-07-13 9:11 ` Arnout Vandecappelle
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=20170714103518.66ca2b7e@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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