From: "André A. Gomes" <andremegafone@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 67655@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#67655] [PATCH]: Update webkitgtk to 2.42.3
Date: Tue, 12 Dec 2023 10:15:33 +0200 [thread overview]
Message-ID: <87y1dz3kgq.fsf@gmail.com> (raw)
In-Reply-To: <bc06c7c38fc68567dcbf01e33ccd129ed35ec4c9.camel@gmail.com> (Liliana Marie Prikler's message of "Fri, 08 Dec 2023 20:55:40 +0100")
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> The webkitgtk-* family collectively accounts for more than 600
> rebuilds, three of them being webkit (i.e. you'll wait 10 hours while
> your machine nearly dies grasping for more RAM). Even with a graft,
> I'd first verify that it builds on CI.
>
> Plus, I don't see how this series accounts for webkitgtk-next, i.e. the
> GTK4 variant. We have that over at gnome-team already, but a
> nontrivial amount of work went into getting it into a functional state.
> I've cherry-picked them onto a wip-webkit branch now. Hopefully we can
> merge that faster than gnome itself.
As Leo mentioned, WebKitGTK updates are paramount from a security point
of view. But I understand the constraints that Liliana mentions. Is
there anything I can do to help? It's hard for me to grasp the full
picture that you describe. Thanks.
--
André A. Gomes
"You cannot even find the ruins..."
next prev parent reply other threads:[~2023-12-12 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 8:10 [bug#67655] [PATCH]: Update webkitgtk to 2.42.3 André A. Gomes
2023-12-08 18:08 ` Liliana Marie Prikler
2023-12-08 18:41 ` Leo Famulari
2023-12-08 19:55 ` Liliana Marie Prikler
2023-12-12 8:15 ` André A. Gomes [this message]
2023-12-12 17:56 ` Liliana Marie Prikler
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=87y1dz3kgq.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=67655@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=liliana.prikler@gmail.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.