From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Adrian Perez de Castro <aperez@igalia.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] bump webkitgtk
Date: Fri, 5 Jan 2024 10:11:05 +0100 [thread overview]
Message-ID: <20240105101105.6a181dcd@windsurf> (raw)
In-Reply-To: <CACXRmJirxfxvBcAV0cyzw+CmOzC7F4sSSOv0Po8zLxMaCndrfQ@mail.gmail.com>
Hello Thomas,
On Fri, 5 Jan 2024 10:06:54 +0100
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> I have an open patch series to bump webkitgtk, which has been open for a while.
> https://patchwork.ozlabs.org/project/buildroot/list/?series=381656
>
> The patches have been tested and acknowledged by Adrian. Ideally, the
> series will get merged before the 2024.02 window, which is the next
> LTS. What do you think?
I agree. We have lots of webkitgtk patches, including some fixes (some
of which haven't been looked at by Adrian I believe).
> I also saw that cairo is outdated, for which I also have a patch.
> (https://patchwork.ozlabs.org/project/buildroot/patch/20240102090933.64969-1-thomas.devoogdt@barco.com/)
> That one is a bit more tricky since the build system has been changed
> upstream. So I can use an additional pair of eyes to check that one.
I also saw this patch. My initial reaction is that I would have
preferred a staged approach, where we first bump to a version that
supports autotools and meson in one patch, then switch from autotools
to meson in one patch (without bumping), then bump again to whatever
latest version. This would have made review slightly easier. However, I
agree this is quite a bit of additional work, on top of very good work
you've already done, so I think we should just bite the bullet and look
at what you did, even if it's in a single patch.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-05 9:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 9:06 [Buildroot] bump webkitgtk Thomas Devoogdt
2024-01-05 9:11 ` Thomas Petazzoni via buildroot [this message]
2024-01-06 13:47 ` [Buildroot] [PATCH v5 1/3] package/cairo: bump to 1.17.4 Thomas Devoogdt
2024-01-06 13:47 ` [Buildroot] [PATCH v5 2/3] package/cairo: move to the meson build system Thomas Devoogdt
2024-01-06 13:48 ` [Buildroot] [PATCH v5 3/3] package/cairo: bump to 1.18.0 Thomas Devoogdt
2024-01-07 10:55 ` [Buildroot] [PATCH v6 1/3] package/cairo: bump to 1.17.4 Thomas Devoogdt
2024-01-07 10:55 ` [Buildroot] [PATCH v6 2/3] package/cairo: move to the meson build system Thomas Devoogdt
2024-01-16 22:39 ` Adrian Perez de Castro
2024-02-05 14:49 ` Peter Korsgaard
2024-02-05 21:22 ` [Buildroot] [PATCH v7 1/2] " Thomas Devoogdt
2024-02-05 21:23 ` [Buildroot] [PATCH v7 2/2] package/cairo: bump to 1.18.0 Thomas Devoogdt
2024-02-05 21:30 ` [Buildroot] [PATCH v8 1/2] package/cairo: move to the meson build system Thomas Devoogdt
2024-02-05 21:30 ` [Buildroot] [PATCH v8 2/2] package/cairo: bump to 1.18.0 Thomas Devoogdt
2024-02-07 16:17 ` [Buildroot] [PATCH v8 1/2] package/cairo: move to the meson build system Peter Korsgaard
2024-02-07 19:15 ` Thomas Devoogdt
2024-02-07 19:31 ` [Buildroot] [PATCH v9 " Thomas Devoogdt
2024-02-07 19:31 ` [Buildroot] [PATCH v9 2/2] package/cairo: bump to 1.18.0 Thomas Devoogdt
2024-07-14 22:07 ` [Buildroot] [PATCH v9 1/2] package/cairo: move to the meson build system Arnout Vandecappelle via buildroot
2024-07-17 18:09 ` Thomas Petazzoni via buildroot
2024-07-17 21:07 ` Thomas Devoogdt
2024-01-07 10:55 ` [Buildroot] [PATCH v6 3/3] package/cairo: bump to 1.18.0 Thomas Devoogdt
2024-01-16 22:39 ` Adrian Perez de Castro
2024-01-16 22:38 ` [Buildroot] [PATCH v6 1/3] package/cairo: bump to 1.17.4 Adrian Perez de Castro
2024-02-05 14:38 ` Peter Korsgaard
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=20240105101105.6a181dcd@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.com \
--cc=yann.morin.1998@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox