unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: "Philip McGrath" <philip@philipmcgrath.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	guix-devel@gnu.org, "Andreas Enge" <andreas@enge.fr>
Subject: Re: Qt in core-updates (was: KDE in core-updates)
Date: Mon, 27 Feb 2023 21:02:24 +0200	[thread overview]
Message-ID: <Y/z+QHcEIpuP7oQZ@3900XT> (raw)
In-Reply-To: <993924cc-84ac-da98-a199-fb229f45fd70@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

On Sun, Feb 26, 2023 at 09:38:43PM -0500, kiasoc5 wrote:
> On 2/26/23 18:43, Philip McGrath wrote:
> > Hi,
> > 
> > On Sunday, February 26, 2023 7:44:20 AM EST Andreas Enge wrote:
> > > 
> > > In any case, I realised that we are still compiling most packages (including
> > > KDE) with Qt 5, which is seriously outdated (not maintained any more in the
> > > free version since May 2021). Qt 6.3 support will end in April 2023, that
> > > of the current version Qt 6.4 in September 2023. So we have the work carved
> > > out for a (yet to be created) Qt/KDE team.
> > > 
> > 
> > Note that KDE maintains a patch collection for Qt 5.15:
> > https://community.kde.org/Qt5PatchCollection
> > 
> > There was an announcement here:
> > https://dot.kde.org/2021/04/06/announcing-kdes-qt-5-patch-collection
> > 
> > Patches are exclusively backports of bugfixes that have already been committed
> > to upstream Qt 6, except that patches for Qt 5.15 components removed in Qt 6
> > are also accepted. The patches are curated by a small group of KDE developers
> > who also have commit privileges in the upstream Qt Project (as distinct from
> > the Qt Company).
> > 
> > I think out Qt 5 packages should be based on the KDE patch collection.
> > 
> > The patches are maintained in Git repositories with the same structure as
> > upstream Qt. They could be extracted with `git format-patch v5.15.3-lts-
> > lgpl..origin/kde/5.15` and added to "gnu/packages/patches/", or we could just
> > change the origins for Qt 5 to point to KDE's repositories, e.g. this one for
> > qt-base: https://invent.kde.org/qt/qt/qtbase/-/tree/kde/5.15
> 
> The KDE patchset moves quickly and does not have tagged releases. If that
> proves difficult we could also just bump the QT5 version to 5.15.8, which is
> freely available.

This is something we should probably do anyway.

We should also try to keep qtwebengine patched as much as possible,
since it is a web engine :)

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-27 19:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 13:59 KDE in core-updates Andreas Enge
2023-02-24 10:34 ` Andreas Enge
2023-02-25 18:19   ` Ludovic Courtès
2023-02-26 12:44     ` Qt in core-updates (was: KDE in core-updates) Andreas Enge
2023-02-26 23:43       ` Philip McGrath
2023-02-27  2:38         ` kiasoc5
2023-02-27 19:02           ` Efraim Flashner [this message]
2023-02-28 15:13             ` Andreas Enge
2023-02-28 17:59               ` Qt in core-updates Andreas Enge
2023-02-28 18:09               ` Andreas Enge
2023-02-28 18:20                 ` Leo Famulari
2023-02-28 20:51                   ` Andreas Enge
2023-02-28 20:55                     ` Andreas Enge
2023-02-28 23:54                       ` Andreas Enge
2023-03-01  0:05                         ` Andreas Enge
2023-03-15 13:53 ` KDE " Andreas Enge

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=Y/z+QHcEIpuP7oQZ@3900XT \
    --to=efraim@flashner.co.il \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=kiasoc5@disroot.org \
    --cc=ludo@gnu.org \
    --cc=philip@philipmcgrath.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).