All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nimai Mahajan <nimaim@gmail.com>
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 17:42:57 +0000	[thread overview]
Message-ID: <CALoSW672Hh1KbdDRWE72JjZn4ajqM1zdFuNakGEJ3G0XM=g6hQ@mail.gmail.com> (raw)
In-Reply-To: <20180225172619.GA2276@scaer>

On Sun, Feb 25, 2018, 12:26 PM Yann E. MORIN <yann.morin.1998@free.fr>
wrote:

> Arnout, All,
>
> On 2018-02-25 18:06 +0100, Arnout Vandecappelle spake thusly:
> > 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?
>
> Yes, I do object it.
>
> As you said, this is the last version that was GPL-2/LGPL-2.1 (for most
> parts), so removing it means some companies will be left out in the
> cold, not being able to update.
>
> This was one of the most important reasons this choice was added.
>

I completely overlooked the bump to LGPLv3, my apologies. As mentioned, it
forces many companies to use the commercial license due to much more
stringent rules, which is unacceptable.

That being said, we use Qt at work on a daily basis and 5.6 is missing tons
of new features and security updates, which forced us to move to 5.9.x.
5.9.x added the new qt quick controls 2 embedded controls, which just about
every project today is using, especially on embedded devices that are
resource limited. But yes many projects are also still using 5.6.

I think the only compromise here is to rework the Qt build system to leave
the Qt 5.6.x LTS series (legacy LTS), add in Qt 5.9.x LTS (latest LTS), and
Qt 5.10.x as the bleeding edge / latest. I'm not sure how others feel about
that though and how much work that is. It's not trivial to test all 3
versions on the myriad of architectures and platforms Buildroot supports.


> Regards,
> Yann E. MORIN.
>
> --
>
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
> conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___
>      |
> | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is
> no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v
>  conspiracy.  |
>
> '------------------------------^-------^------------------^--------------------'
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180225/50e911f6/attachment.html>

  reply	other threads:[~2018-02-25 17:42 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     ` [Buildroot] Drop support for Qt 5.6? [was: [RFC 1/2] qt5: bump latest version to 5.10.0] Arnout Vandecappelle
2018-02-25 17:17       ` Baruch Siach
2018-02-25 17:26       ` Yann E. MORIN
2018-02-25 17:42         ` Nimai Mahajan [this message]
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='CALoSW672Hh1KbdDRWE72JjZn4ajqM1zdFuNakGEJ3G0XM=g6hQ@mail.gmail.com' \
    --to=nimaim@gmail.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 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.