From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Drop support for Qt 5.6? [was: [RFC 1/2] qt5: bump latest version to 5.10.0]
Date: Sun, 25 Feb 2018 18:06:37 +0100 [thread overview]
Message-ID: <78215947-020b-17da-27d8-89bcdfe1c859@mind.be> (raw)
In-Reply-To: <1518442630960-0.post@n4.nabble.com>
On 12-02-18 14:37, nimaim wrote:
> This is semi unrelated, but along would this, would it make sense to bump the
> current Qt LTS version from 5.6.x to 5.9.x (currently 5.9.4, which should
> also be bumped from the 5.9.3 currently in the BR repo), and use this 5.10.x
> version as BR2_PACKAGE_QT5_VERSION_LATEST as currently proposed?
The problem is that 5.6.x is the last version that still was LGPL-2.0. For some
companies this could be a problem.
That said, I'm not particularly in favour of keeping old, unmaintained and
probably vulnerable versions of packages just for companies' irrational fears of
3.0. It is clear from all the conditions we currently have that such maintenance
does not come for free...
So, any objections to replace Qt 5.6 with Qt 5.9?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2018-02-25 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 16:13 [Buildroot] [RFC 0/2] Qt5 bump latest version to 5.10.0 Gaël PORTAY
2018-02-11 16:13 ` [Buildroot] [RFC 1/2] qt5: " Gaël PORTAY
2018-02-12 13:37 ` nimaim
2018-02-25 17:06 ` Arnout Vandecappelle [this message]
2018-02-25 17:17 ` [Buildroot] Drop support for Qt 5.6? [was: [RFC 1/2] qt5: bump latest version to 5.10.0] Baruch Siach
2018-02-25 17:26 ` Yann E. MORIN
2018-02-25 17:42 ` Nimai Mahajan
2018-02-25 17:52 ` Yann E. MORIN
2018-02-25 18:10 ` Nimai Mahajan
2018-02-25 18:28 ` Yann E. MORIN
2018-02-25 18:29 ` Nimai Mahajan
2018-02-26 8:22 ` Peter Korsgaard
2018-02-26 11:50 ` Nimai Mahajan
2018-02-26 12:14 ` Peter Korsgaard
2018-02-26 12:17 ` Nimai Mahajan
2018-02-26 20:45 ` Nimai Mahajan
2018-02-26 8:18 ` Peter Korsgaard
2018-02-12 21:07 ` [Buildroot] [RFC 1/2] qt5: bump latest version to 5.10.0 Gaël PORTAY
2018-02-11 16:13 ` [Buildroot] [RFC 2/2] qt5webengine: select libnss Gaël PORTAY
2018-02-12 21:19 ` Gaël PORTAY
2018-02-11 22:11 ` [Buildroot] [RFC 0/2] Qt5 bump latest version to 5.10.0 Julien CORJON
2018-02-12 18:20 ` Gaël PORTAY
2018-02-12 22:20 ` Gaël PORTAY
2018-02-13 15:23 ` Gaël PORTAY
2018-02-13 16:35 ` Gaël PORTAY
2018-02-19 22:58 ` Gaël PORTAY
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=78215947-020b-17da-27d8-89bcdfe1c859@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.