unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip McGrath <philip@philipmcgrath.com>
To: Florian Bruhin <me@the-compiler.org>,
	Jaft <wamm_kd_schmelingski@yahoo.com>,
	Leo Famulari <leo@famulari.name>,
	53011@debbugs.gnu.org
Subject: bug#53011: Possible to Update qtbase-5 to v5.15.8?
Date: Wed, 5 Jan 2022 02:07:48 -0500	[thread overview]
Message-ID: <dbddd30e-7507-bbb3-aa69-0a3691214459@philipmcgrath.com> (raw)
In-Reply-To: <20220104180457.tgkrnle4nc6ougdr@aragog>

Hi,

On 1/4/22 13:04, Florian Bruhin wrote:
> Hey,
> 
> qutebrowser upstream here.
> 
> On Tue, Jan 04, 2022 at 05:35:54PM +0000, Jaft wrote:
>> Partially because it's the latest version but primarily because there's a bug in the current version for QTwebengine.
> 
> Note that qtbase releases after 5.15.2 are commercial-only
> unfortunately:
> 
> https://www.qt.io/blog/qt-offering-changes-2020
> https://www.qt.io/blog/commercial-lts-qt-5.15.3-released
> 
> However, QtWebEngine source releases are exempt from that, due to
> containing third-party LGPL code, so its source for newer releases is
> publicly available:
> https://code.qt.io/cgit/qt/qtwebengine.git/refs/tags
> 
> Most distributions I'm aware of are still keeping updated with those
> releases, as they should work just fine against an older qtbase.
> 
> Alternatively, to fix the issues with missing text, backporting this
> patch should suffice:
> https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/374232
> 
> However, newer QtWebEngine releases come with a variety of security
> fixes and even a Chromium upgrade (from 83 to 87), so I'd highly
> recommend keeping it up to date.
> 
> Florian
> 

As some of you may know, KDE maintains a carefully curated patch 
collection for Qt 5 consisting strictly of backports from the current 
(QT6-based) development branch of Qt and fixes for removed 
functionality. (They do not increment the Qt version number, to avoid 
any further confusion.) AIUI, this is the same way The Qt Company 
creates their non-public releases for customers using non-free licenses 
(or at least it's what they say they do), though the KDE developers, 
quite reasonably, only backport patches of interest to free software.

Announcement: 
https://dot.kde.org/2021/04/06/announcing-kdes-qt-5-patch-collection
FAQ: https://community.kde.org/Qt5PatchCollection

Using these patches should be as easy as pointing the origin of the 
relevant Guix packages to the kde/5.15 branches of the corresponding 
repositories, e.g. <https://invent.kde.org/qt/qt/qtbase/-/tree/kde/5.15>.

I think this would be the best way to update Guix's qtbase-5 and other 
packages in general. But, as Florian explains, the situation with 
QtWebEngine is even less complicated.

-Philip




  reply	other threads:[~2022-01-05  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28974452.1530175.1641317754644.ref@mail.yahoo.com>
2022-01-04 17:35 ` bug#53011: Possible to Update qtbase-5 to v5.15.8? Jaft via Bug reports for GNU Guix
2022-01-04 18:03   ` Leo Famulari
2022-01-04 18:04   ` Leo Famulari
2022-01-04 18:04   ` Florian Bruhin
2022-01-05  7:07     ` Philip McGrath [this message]
2022-01-05 19:08     ` Leo Famulari
2022-01-05 19:09       ` Leo Famulari
2022-02-02 19:15         ` Jaft via Bug reports for GNU Guix
2022-01-04 20:32   ` Florian Bruhin
2022-01-05 19:10   ` bug#53011: [PATCH] gnu: Fix text rendering in QtWebEngine Leo Famulari
2022-07-01 22:08   ` bug#53011: Qt patches for 5.15.5 phodina via Bug reports for GNU Guix
2023-03-29  0:38   ` bug#53011: Possible to Update qtbase-5 to v5.15.8? Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dbddd30e-7507-bbb3-aa69-0a3691214459@philipmcgrath.com \
    --to=philip@philipmcgrath.com \
    --cc=53011@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=me@the-compiler.org \
    --cc=wamm_kd_schmelingski@yahoo.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).