From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5: bump latest version to 5.9.1
Date: Fri, 14 Jul 2017 15:49:15 +0200 [thread overview]
Message-ID: <87tw2f9lic.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170714153641.0e0af325@windsurf> (Thomas Petazzoni's message of "Fri, 14 Jul 2017 15:36:41 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> As long as we can find a solution for this problem I don't think we
>> should move to sperate files for license hashes. We have 2k+ packages
>> and only a very small subset of those have a version selection (and only
>> a small subset of that subset will change the license text between
>> versions), so I prefer a less-clean solution for this special case
>> instead of adding 2k+ extra files to the tree.
> Yes, true.
> So perhaps the easy solution is to search for a hash file in the
> version-specific sub-folder. If it exists, use it (and only this one).
> If it doesn't exist, fallback to the one in the package directory.
Yes, makes sense to me.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-07-14 13:49 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
2017-07-14 13:12 ` Peter Korsgaard
2017-07-14 13:36 ` Thomas Petazzoni
2017-07-14 13:49 ` Peter Korsgaard [this message]
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=87tw2f9lic.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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