From: Andreas Enge <andreas@enge.fr>
To: kiasoc5 <kiasoc5@disroot.org>,
"Philip McGrath" <philip@philipmcgrath.com>,
"Ludovic Courtès" <ludo@gnu.org>,
guix-devel@gnu.org
Subject: Re: Qt in core-updates (was: KDE in core-updates)
Date: Tue, 28 Feb 2023 16:13:52 +0100 [thread overview]
Message-ID: <Y/4aMLnC/3jY3je9@jurong> (raw)
In-Reply-To: <Y/z+QHcEIpuP7oQZ@3900XT>
Hello Philip, Kiasoc5, Efraim,
thanks a lot for your input!
Indeed I got my information that Qt 5 was phased out from Wikipedia,
which mentioned May 2021 as the end of support. I did not expect there
to be more versions! But then discovered the 5.15.8 version, probably
related to the commercial support available until May this year?
Anyway, I updated in my own branch wip-andreas-core-updates (since I wanted
to avoid rebuilding core-updates with its recent world-rebuilding changes);
just qtwebengine takes 6 hours on my laptop... (And it required the update,
since it would not build at version 5.15.5.) Now I am trying to build all
the Qt packages before applying the patch to core-updates; it looks good
so far.
Andreas
next prev parent reply other threads:[~2023-02-28 15:14 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
2023-02-28 15:13 ` Andreas Enge [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y/4aMLnC/3jY3je9@jurong \
--to=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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.